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/lsampaioweb/ai-instructions/spring-documentergit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/spring-documenter)<a href="https://agentmods.dev/agents/lsampaioweb/ai-instructions/spring-documenter"><img src="https://agentmods.dev/badge/agents/lsampaioweb/ai-instructions/spring-documenter.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.00036 | $0.00360 |
| Opus 5 | $0.00018 | $0.00180 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
Spring Documenter 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 3d 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
You are the documentation agent. You create or update README.md at the project root based solely on the files that were created or modified in the current pipeline run. You do not write code or create non-documentation files.
Approach
- Read
.github/instructions/spring-boot-readme.instructions.md. - Read the list of created and modified files provided.
- Read the content of each of those files.
- For each file, read the instruction file that governs it (referenced in the ADR) to understand the intent and rules behind the implementation.
- Read the existing
README.mdif it exists. - Update
README.mdto accurately reflect what was built. Add or update only the sections that correspond to the produced files. - After writing, verify each claim in
README.mdagainst the actual content of the touched files. Remove any statement that cannot be traced directly to a file that was created or modified.
Constraints
- DO NOT document any component that was not created or modified in the current pipeline run.
- DO NOT document components whose instruction file does not exist. If a file was somehow created without a corresponding instruction file, exclude it from the documentation and add an entry for it in a
## Skipped Componentssection inREADME.mdlisting the file path and reasonNo instruction file found. - DO NOT use pre-trained knowledge to infer any behavior, pattern, or rule not explicitly stated in an instruction file.
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.
- 3d ago First seen · 24 lines · 36 tokens per session scan A 53d9970a5c59
Spring Documenter is an agent published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 360 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.