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 girijashankarj/cursor-handbook --skill architecture-docsgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/architecture-docs)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/architecture-docs"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/architecture-docs/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/girijashankarj/cursor-handbook/architecture-docs"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/architecture-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.00654 |
| Opus 5 | $0.00013 | $0.00327 |
| Sonnet 5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
architecture-docs 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Create Architecture Documentation
Trigger
When the user needs to document system architecture or make Architecture Decision Records (ADRs).
Prerequisites
- Codebase or design available to analyze
- docs/ or docs/architecture/ directory exists (or create it)
- Mermaid support in docs (GitHub, MkDocs, etc.)
Steps
Step 1: System Overview
- High-level architecture diagram (Mermaid)
- List all services/components
- Document communication patterns
- Document data flow
Step 2: Component Documentation
For each service/component:
- Purpose and responsibilities
- Technology stack
- API contracts (if applicable)
- Data stores
- Dependencies
- Scaling characteristics
Step 3: Architecture Decision Records (ADRs)
For significant decisions:
- Title: Short descriptive title
- Status: Proposed / Accepted / Deprecated / Superseded
- Context: Why this decision is needed
- Decision: What was decided
- Consequences: Trade-offs and implications
ADR template:
# ADR-{number}: {title}
## Status
{Proposed | Accepted | Deprecated | Superseded by ADR-{n}}
## Context
{What is the issue that we're seeing that is motivating this decision?}
## Decision
{What is the change that we're proposing and/or doing?}
## Consequences
{What becomes easier or harder because of this change?}
Step 4: Data Flow Diagrams
- Request flow through the system
- Event/message flow
- Data pipeline flow
- Authentication flow
Step 5: Operational Documentation
- Deployment architecture
- Monitoring and alerting overview
- Disaster recovery plan
- Scaling procedures
Completion Checklist
- At least one diagram (Mermaid) for system or data flow
- ADRs for significant decisions (format, status, context, decision, consequences)
- Component list with purpose and tech stack
- Operational section (deploy, monitor, scale)
If Step Fails
- Step 1 (overview): Start with 3–5 boxes; add detail later. Use
flowchart LRorflowchart TBfor simple flows - Step 3 (ADRs): Number format
ADR-001; keep each ADR to one decision - Step 4 (diagrams): Mermaid syntax: no spaces in node IDs; use
A[Label]notA[Label with spaces]
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.
- 5d ago First seen · 83 lines · 26 tokens per session scan A 05fad8a8c4e4
architecture-docs is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 654 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
mobile-rn-screen
Polish an existing React Native screen to feel intentional, native, and human-crafted. Use for "this screen looks off", "feels clunky on iOS", "Android version looks wrong", "jank when scrolling", "button is unreachable", or any RN-specific UX polish pass.
mobile-emulator-test
QA a native Android build end-to-end on the emulator. Use for "test on emulator", "QA Android build", "verify native build", "white screen", "cache rehydration", "Expo dev-client QA", "adb reverse". Pairs Metro/adb walk with Supabase + Sentry MCPs for three-layer CRUD verification.
design-generative-art
Create original algorithmic visuals with p5.js, Canvas, or SVG using seeded randomness and interactive controls. Use when "generative art", "procedural visuals", "flow fields", "particle system", or "art from code". Data charts → data-visualization. UI illustration → design-frontend.
audit-security
Static OWASP review of app code (injection, headers, deps). Use when "review security" or "check vulnerabilities". Session/route×gate/getSession → audit-auth-flows. Plan-only burndown → plan-security-audit. Table RLS → plan-rls-audit. LLM attacks → audit-llm-security.