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/0xrafasec/ai-workflow/architecturenpx skills add 0xrafasec/ai-workflow --skill architecturegit clone --depth 1 https://github.com/0xrafasec/ai-workflowWrote 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/0xrafasec/ai-workflow/architecture)<a href="https://agentmods.dev/skills/0xrafasec/ai-workflow/architecture"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/architecture.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.00075 | $0.00923 |
| Opus 5 | $0.00037 | $0.00462 |
| Sonnet 5 | $0.00015 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
architecture 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create the system architecture document. Argument: $ARGUMENTS
Context Gathering
Before interviewing, read what already exists:
-
Check for existing docs:
- Read
docs/PRD.mdordocs/prd/if they exist - Read
docs/ARCHITECTURE.md— if revising, don't start from scratch - Read
README.md,CLAUDE.md - Read any whitepaper, design doc, or existing architecture doc
- Read
-
If no docs exist (inherited project):
- Read
README.mdfor project overview - Explore the directory structure to understand the codebase layout
- Read key entry points (main files, route definitions, config files)
- Check
git log --oneline -20for recent direction - Read
package.json,Cargo.toml,pyproject.toml, or equivalent for dependencies and project metadata - Summarize what you learned to the user before starting the interview — "Here's what I understand about this project so far: ..."
- Read
Interview
Use AskUserQuestion to dig into the system design. Adapt questions based on what you already learned from the codebase.
- Components — What are the main components/services/modules? How do they communicate? What are the trust boundaries?
- Data flow — How does data enter the system, get processed, and get stored? What are the critical paths?
- Technology choices — What stack and why? What are the hard constraints vs preferences?
- Deployment — How does this run? Single binary, microservices, serverless? Where (cloud, on-prem, edge)?
- Scaling and performance — What are the expected loads? Where are the bottlenecks? What needs to be fast?
- Integration points — What external systems does this talk to? What APIs does it expose? What does it depend on?
- Key decisions — What architectural decisions have already been made? What tradeoffs were accepted and why?
For inherited projects, focus more on: "Is my understanding correct?" and "What would you change?" rather than "What do you want?"
Write
Write to docs/ARCHITECTURE.md:
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 · 98 lines · 75 tokens per session scan A 284b4e341b11
architecture is a skill published in the GitHub repository 0xrafasec/ai-workflow (9 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 923 once invoked, about $0.0004 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…