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 agentmods add skills/future-cx/ai-architecture-toolkit/create-an-agentnpx skills add Future-CX/AI-Architecture-Toolkit --skill create-an-agentgit clone --depth 1 https://github.com/Future-CX/AI-Architecture-ToolkitWrote 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/future-cx/ai-architecture-toolkit/create-an-agent)<a href="https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/create-an-agent"><img src="https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/create-an-agent.svg" alt="Measured on agentmods" 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.00036 | $0.00397 |
| Opus 5 | $0.00018 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
create-an-agent 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 6d 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.
What it actually says
Create An Agent
Quick Start
Create agent definitions under agents/ using the preset template in templates/agent-template.md.
Use the helper script when the requested agent has a clear name, purpose, and responsibilities:
python3 skills/create-an-agent/scripts/create-agent.py "Data Architect" \
--purpose "Support data architecture decisions across platforms, ownership, quality, and governance." \
--responsibility "Clarify data ownership, domains, and critical data flows." \
--responsibility "Assess data quality, privacy, retention, and lineage needs." \
--responsibility "Review analytics, integration, and operational data implications."
This creates agents/data-architect-agent.md.
Workflow
- Determine the agent name and convert it to
<slug>-agent.md. - Capture a one-sentence purpose.
- Capture 3-7 concrete responsibilities.
- Generate the file under
agents/using the preset template. - Do not overwrite an existing agent file unless the user explicitly asks.
- Keep the style consistent with the existing files in
agents/. - Update the Agents table in the top-level
README.mdwhenever an agent is created or updated.
Output Standard
Each agent file must use this structure:
# Agent Name
## Purpose
One-sentence purpose.
## Recommended Model
Use a frontier reasoning model for complex architecture decisions, tradeoff analysis, and review preparation. Use a faster general-purpose model for drafting, summarization, and checklist-based reviews.
## Responsibilities
- Responsibility one.
- Responsibility two.
- Responsibility three.
Template
Use templates/agent-template.md as the source template for generated agent files.
What ships with it
3 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.
- 6d ago First seen · 59 lines · 36 tokens per session scan A b137780378ad
create-an-agent is a skill published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 397 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…