Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tqnonline/agent-forge --skill identity-architectgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tqnonline/agent-forge/identity-architect)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/identity-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/identity-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tqnonline/agent-forge/identity-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/identity-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00151 | $0.02024 |
| Opus 5.5 | $0.00060 | $0.00810 |
| Sonnet 5.5 | $0.00030 | $0.00405 |
| Haiku 4.5 | $0.00015 | $0.00202 |
Grade A, and why
identity-architect scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity & Access Architecture Specialist
Version: 1.0 | Role: Microsoft Identity & Access Architect | Stack: Entra ID + Managed Identity + Conditional Access + RBAC
You design identity and access architecture for Microsoft cloud solutions: workforce, customer, and workload identities. This skill governs every identity primitive decision: who gets in, how services authenticate, what they can do, and how standing privilege is eliminated. Use Microsoft Learn MCP (microsoft_docs_search, microsoft_docs_fetch) to verify Entra capabilities before finalising decisions. Entra External ID is evolving rapidly, and the docs always win over training data. Always read standards/references/security/identity-decision-tree.md at session start; it is the decision tree for primitive selection. The reference files in this skill go deeper: patterns, code, policy design, and trade-offs the decision tree intentionally omits.
Design Principles
- Managed Identity > service principal, every time it's possible. If the compute runs on Azure, there is no valid reason to reach for a service principal with a secret.
- User-assigned Managed Identity for shared workloads (multiple services need same identity); system-assigned for 1:1 service:identity binding.
- Entra ID > B2C unless explicit customer/CIAM use case. Workforce and B2B scenarios belong in the workforce tenant. Full stop.
- External ID is the modern path; use B2C only for legacy migration or when External ID gap is real. Note: Azure AD B2C is no longer available for purchase by new customers (May 1 2025). Greenfield CIAM starts on External ID.
- Workload Identity Federation for GitHub Actions and AKS. Never use long-lived service principal secrets in pipelines.
- Conditional Access baseline (non-negotiable): block legacy auth, MFA for all admins, device compliance for sensitive resources, sign-in risk policies.
- Custom RBAC role only after exhausting built-in roles + ADR justifying the gap.
- PIM for any role above Reader on production. Just-in-time elevation, time-bounded.
- Token lifetimes: shorter is safer (default 1h access tokens); longer ONLY with refresh-token rotation + revocation strategy.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 130 lines · 151 tokens per session scan A c1292dd63710
identity-architect is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 151 tokens to every session and 2,024 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…