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 skills/projanvil/mindforge/tech-documentationnpx skills add ProjAnvil/MindForge --skill tech-documentationgit clone --depth 1 https://github.com/ProjAnvil/MindForgeWhat 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.00051 | $0.01381 |
| Opus 5 | $0.00026 | $0.00691 |
| Sonnet 5 | $0.00010 | $0.00276 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
tech-documentation 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 yesterday.
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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Documentation Skill
Technical documentation writing expertise, providing comprehensive methodology and templates for producing high-quality technical documentation.
Overview
This is a comprehensive skill module focused on technical documentation writing, covering standards, templates, and best practices for various types of technical documentation to help teams produce high-quality, easy-to-understand, and maintainable documentation.
Core Capabilities
1. API Documentation
- OpenAPI/Swagger Specifications
- RESTful API Documentation
- GraphQL Documentation
- gRPC Interface Documentation
- API Change Logs
- Authentication and Authorization Documentation
2. Architecture Documentation
- Architecture Design Documents (ADD)
- Architecture Decision Records (ADR)
- System Architecture Diagrams (C4 Model, UML)
- Technology Selection Reports
- Architecture Evolution Roadmaps
3. Detailed Design Documents
- Module Design Documents
- Database Design Documents
- Interface Design Documents
- Algorithm Design Specifications
- Sequence Diagrams/Flowcharts
4. Deployment and Operations Documentation
- Deployment Manuals
- Operations Manuals
- Incident Response Manuals
- Monitoring and Alerting Configuration
- Performance Optimization Guides
- Backup and Recovery Procedures
5. User Manuals
- Product User Manuals
- Quick Start Guides
- Frequently Asked Questions (FAQ)
- Troubleshooting Guides
- Best Practices
6. Developer Documentation
- Contributing Guidelines (CONTRIBUTING.md)
- Coding Standards
- Development Environment Setup
- Testing Guides
- Release Processes
7. Project Management Documentation
- Project Plans
- Requirements Documents
- Test Plans
- Release Notes
- Change Logs (CHANGELOG)
8. Knowledge Base Documentation
- Technical Blog Posts
- Case Studies
- Problem Summaries
- Learning Notes
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 227 lines · 51 tokens per session scan A 798fd4178bd9
tech-documentation is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,381 once invoked, about $0.0003 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 skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).