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 agents/rohanmistry231/claude-code-project-structure-learning-repository/readmegit clone --depth 1 https://github.com/rohanmistry231/Claude-Code-Project-Structure-Learning-RepositoryWrote 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/agents/rohanmistry231/claude-code-project-structure-learning-repository/readme)<a href="https://agentmods.dev/agents/rohanmistry231/claude-code-project-structure-learning-repository/readme"><img src="https://agentmods.dev/badge/agents/rohanmistry231/claude-code-project-structure-learning-repository/readme.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 | $0.00000 | $0.01031 |
| Opus 5 | $0.00000 | $0.00515 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
README 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.claude/agents/ — Sub-Agents
Sub-agents are specialist Claude instances that the main Claude agent can spawn to handle a focused, isolated task.
Think of them like calling in a specialist consultant: the main Claude is a generalist handling your conversation, and it can call a sub-agent that has one narrow job and does it very thoroughly.
How Sub-Agents Work
You: "do a security audit before we deploy"
↓
Main Claude decides this needs the security-reviewer agent
↓
Main Claude spawns security-reviewer as a sub-process
↓
security-reviewer reads the codebase with its own focused checklist
↓
security-reviewer returns a structured report to main Claude
↓
Main Claude presents the findings to you
The sub-agent runs independently — it has its own context, its own instructions, and its own output format. It does not share the main conversation's context.
What Goes in an Agent File
An agent file is a Markdown file in .claude/agents/ that defines:
# Agent: <Name>
## Description
What this agent does and what it specialises in.
## When to Use
When should the main Claude spawn this agent?
## Agent Instructions
The detailed, step-by-step checklist the agent follows.
## Output Format
The exact structure the agent must use in its response.
The security-reviewer Agent (This Project)
File: .claude/agents/security-reviewer.md
This agent performs a dedicated security audit with five checklists:
| Checklist | What it looks for |
|---|---|
| Auth & Authorization | Routes missing token verification, ownership checks |
| Input Validation | SQL injection via string interpolation, unsafe file uploads |
| Sensitive Data Exposure | Passwords in responses, secrets in logs, raw error messages |
| Configuration | Hardcoded secrets, allow_origins: ["*"], debug mode on |
| Rate Limiting | Missing rate limits on public endpoints, no pagination cap |
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 · 142 lines · 0 tokens per session scan A f086003fa50c
README is an agent published in the GitHub repository rohanmistry231/Claude-Code-Project-Structure-Learning-Repository (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,031 tokens. 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.