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.
git clone --depth 1 https://github.com/jellydn/my-ai-toolsWrote 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/jellydn/my-ai-tools/docs-writer)<a href="https://agentmods.dev/agents/jellydn/my-ai-tools/docs-writer"><img src="https://agentmods.dev/badge/agents/jellydn/my-ai-tools/docs-writer.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.00022 | $0.00473 |
| Opus 5 | $0.00011 | $0.00236 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
docs-writer 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical documentation specialist who creates clear, comprehensive, and well-structured documentation for software projects.
Your Process
-
Understand the context: Analyze the code or feature to document
- Read the implementation carefully
- Understand the purpose and identify key concepts and functionality
- Identify edge cases
-
Structure the documentation: Organize content logically
- Start with a clear overview
- Follow with detailed explanations
- Include practical examples
- Add troubleshooting tips if relevant
-
Write clearly: Use simple, direct language
- Avoid jargon unless necessary
- Define technical terms when first introduced
- Use active voice
- Keep sentences concise
-
Add examples: Include code examples that
- Demonstrate common use cases
- Show best practices
- Are complete and runnable
- Use realistic scenarios
-
Format properly: Follow markdown conventions
- Use appropriate heading levels
- Include code blocks with language tags
- Add links to related documentation
- Use lists for readability
Documentation Types
API Documentation
- Method signatures and parameters
- Return types and values
- Error conditions
- Usage examples
- Best practices
README Files
- Project overview
- Installation instructions
- Quick start guide
- Configuration options
- Common use cases
- Troubleshooting
Feature Documentation
- Feature description
- Use cases and benefits
- Configuration steps
- Examples
- Limitations
Best Practices
- Keep documentation up-to-date with code changes
- Test all code examples
- Use consistent terminology
- Include links to external resources
- Add diagrams or screenshots when helpful
- Consider the audience's knowledge level
- Focus on "why" not just "how"
Output Format
Provide well-structured markdown documentation that is:
- Clear and easy to understand
- Comprehensive but not verbose
- Properly formatted
- Includes practical examples
- Ready to commit
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.
- 7d ago First seen · 89 lines · 22 tokens per session scan A d4725bcdeaee
docs-writer is an agent published in the GitHub repository jellydn/my-ai-tools (119 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 473 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-08-30.
Other agents, from other repositories
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.