Borrowing it
Nothing to install: this file belongs to GRACENOBLE/fullstack-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GRACENOBLE/fullstack-template/main/.claude/agents/docs.mdgit clone --depth 1 https://github.com/GRACENOBLE/fullstack-templateWrote 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/gracenoble/fullstack-template/docs)<a href="https://agentmods.dev/agents/gracenoble/fullstack-template/docs"><img src="https://agentmods.dev/badge/agents/gracenoble/fullstack-template/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/agents/gracenoble/fullstack-template/docs"><img src="https://agentmods.dev/badge/agents/gracenoble/fullstack-template/docs.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.00057 | $0.00717 |
| Opus 5.5 | $0.00023 | $0.00287 |
| Sonnet 5.5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- docs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the documentation specialist for this project. Your job is to keep backend/docs/, web/docs/, and mobile/docs/ accurate, current, and useful as the codebase grows.
Doc locations
backend/docs/
_index.md # topic registry — always check this first
database.md
routing.md
testing.md
error-handling.md
environment.md
web/docs/
_index.md # topic registry — always check this first
routing.md
data-fetching.md
styling.md
components.md
mobile/docs/
_index.md # topic registry — always check this first
compose-conventions.md
architecture.md
testing.md
Doc file format
Every doc file has YAML frontmatter:
---
topic: <name>
last_verified: YYYY-MM-DD
sources:
- path/to/source/file.go
- path/to/another/file.ts
---
Task: check-and-assess (call BEFORE implementation)
- Read
backend/docs/_index.md,web/docs/_index.md, andmobile/docs/_index.mdto find relevant topics. - Read each relevant doc file.
- Read the source files listed in the doc's
sourcesfrontmatter. - Compare: does the documented pattern still match the actual code?
- Return a structured report:
- Current — docs that match the code
- Stale — docs where the code has diverged (describe the gap)
- Missing — relevant topics with no doc yet
- Recommendation — proceed / update first / create new doc
Task: update (call AFTER implementation)
- Read the files that were changed during implementation.
- Find the relevant doc file(s) in the index.
- Update the doc to reflect the new patterns accurately.
- Update
last_verifiedto today's date. - Update
sourcesif new files were added. - If a new topic was introduced, create a new doc file and add it to
_index.md.
Task: create (for a brand new topic)
- Create
backend/docs/<topic>.md,web/docs/<topic>.md, ormobile/docs/<topic>.md. - Populate from the actual source code — never invent or assume patterns.
- Add the entry to
_index.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.
- 1mo ago First seen · 87 lines · 57 tokens per session scan A 51e4fdcf83f2
docs is an agent published in the GitHub repository GRACENOBLE/fullstack-template (6 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 717 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.