Hire an AI identity designer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A threat list of how an agent could be faked, over-trusted or hide what it did
• An identity design for how each agent proves who it is, and how that proof ends or is cancelled
• A permission map showing what each agent may do and how a hand-off narrows it
• A design for an audit log that shows if anyone changed a record
• Deny rules and a list of tests that try to break the design

How it does the job well

• Never accept a claim as proof. "The agent said it was approved" is not authorization. Design for something that can be checked.
• Use established standards. Do not invent new cryptography or signature schemes. Name the standard and say "have a security engineer confirm this against current guidance".
• Deny by default. If identity, permission or the log write cannot be confirmed, the action does not run. If a hand-off chain has a broken link, the whole chain is invalid.
• A hand-off can only narrow permissions, never widen them.
• Keys and secrets never appear in logs, records or replies.
• Name the asset, the threat and the impact before recommending controls.
• Rank findings by real risk (likelihood and impact), with evidence for each.

Mistakes it avoids

• Scoring an agent's trust from what the agent reports about itself.
• Copying the profile's code samples as if they were the user's design.
• Designs for hundreds of agents when the user has two. Match the size they gave you.
• Long lists of generic issues with no evidence they apply.
• Testing or scanning systems without permission.
• Presenting a legal opinion as final.

What a good result looks like

An example, not your task: Your AI agents can spend money, send email, deploy code or call outside tools, and you need clear rules for who may do what.

• Scope. The agents, risky actions, readers of the record and rules the design was built for.
• Threat list. Each way an agent could be faked, over-trusted or hide an action, with the cost and the fix.
• Identity design. How each agent proves who it is, how long that lasts and how it is cancelled.
• Permission and hand-off map. What each agent may do, and the rule that hand-offs can only narrow powers.
• Audit log design. What is recorded for each action and how an edited record would be spotted.
• Deny rules. Conditions that stop an action, and what should raise an alert.

How the work is checked

• Each finding has a location, evidence, severity and a specific fix.
• Likely false positives are checked and removed.
• Items that need a lawyer or auditor are clearly marked.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Build the threat model. It asks how many agents there are, whether they hand work on, what a forged identity could cost and who must trust the record.
• Design identity. It plans how each agent gets a proof of identity, how long it lasts, and how it is renewed or cancelled.
• Design permissions and hand-offs. It sets what each agent may do and makes sure a hand-off can only narrow those powers.
• Design the record. It plans what to log for each action, what the agent meant to do, what it was allowed to do and what happened, with a way to spot edits.
• Set the deny rules. It writes the rules that stop an action when identity, permission or the log cannot be confirmed.
• Write the tests. It lists attacks to try, such as a forged identity, a widened permission or an edited record.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id agentic-identity-trust only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/agentic-identity-trust/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• A list of your agents and what each one can do, in plain words.
• The risky actions, such as moving money, deploying code, changing data or sending messages.
• How the agents talk to each other and which tools you use, such as MCP or a REST API (optional)
• Who needs proof of what happened, such as an auditor, a customer or a regulator (optional)
• Rules you must meet, such as SOC 2 or financial rules (optional)

Helpful context (optional)

• A diagram or a short note on how your agents call each other.
• Your current list of keys, tokens or API credentials that agents use today.
• Any audit or security rules your customers have asked you to meet.

Tools and access

• Claude, ChatGPT or Gemini: A strong reasoning model gives a better threat list. For sample code, use one that can also run code so you can try it.

Functions and deliverables

• AI agent identity designer: Design how your AI agents prove who they are, what they may do and what they did, with a threat list, permission map and tamper-proof log.
  • A threat list of how an agent could be faked, over-trusted or hide what it did
  • An identity design for how each agent proves who it is, and how that proof ends or is cancelled
  • A permission map showing what each agent may do and how a hand-off narrows it
  • A design for an audit log that shows if anyone changed a record
  • Deny rules and a list of tests that try to break the design
  Source: Michael Sitarzewski and Agency Agents contributors.
• AI agent control designer: Set tool permissions, approval rules and an audit log for your AI agent. Get a policy file and a test list before it goes live.
  • A tool table with allow, block or ask-a-human for each tool
  • A policy file in YAML with call limits and blocked text patterns
  • A list of risky requests to flag, with their limits stated
  • The fields to record in your audit log
  • A test list with one test per control
  Source: GitHub Copilot community.
• Customer identity messaging mapper: Map who your customers are and who they want to be, then get copy that reflects it. A customer identity messaging tool for believable wording.
  • A current and aspired identity map
  • An identity gap rating
  • Language patterns that fit
  • Rewritten copy
  Source: sickn33.
• Agent delegation and dependency planner: Plan which AI agent owns each task, who may hand work to whom and what must finish first. Get a delegation plan and failure test cases.
  • A delegation plan: for each handoff, who gets it, why, what they may do and what it waits for
  • An authority and depth check, listing any handoff that would be refused
  • What is logged for each handoff and each refusal
  • A failure checklist
  • Test cases using made-up agents and tasks
  • A list of missing inputs and checks that did not run
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• Your AI agents can spend money, send email, deploy code or call outside tools, and you need clear rules for who may do what.
• One agent hands work to another and you need proof that the first agent allowed it.
• An auditor, a customer or your boss asks how you know what an agent did and that the record was not changed.
• You are about to add agents to a product and want the identity design done before anyone writes code.

Limits to check before starting

• You need to decide if two customer or company records are the same one. Use the Identity graph designer.
• You want sign-in, single sign-on or passkeys for human users. Use the Identity and access engineer.
• You want finished code checked for bugs. Use the Application security reviewer.
• You want it to set up keys, servers or a live system. It writes the design. Your engineers build it and test it.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
• List your agents, what each can do and which actions are risky. Add how they talk to each other if you know. No code access is needed.
• Type "Design identity and trust for these agents. Threat list first. Do not write code unless I ask. Mark anything you assume."
• Read the threat list first. Say which threats matter most, then ask it to run the design again.
• Give the design to a security engineer. Ask them to check every cryptography choice against current standards before anything is built.
• Build it yourself and run the test list. The AI does not run or test anything.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/agentic-identity-trust for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.