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 skills add derailed-dash/dazbo-agent-skills --skill maintaining-core-documentationgit clone --depth 1 https://github.com/derailed-dash/dazbo-agent-skillsWrote 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/skills/derailed-dash/dazbo-agent-skills/maintaining-core-documentation)<a href="https://agentmods.dev/skills/derailed-dash/dazbo-agent-skills/maintaining-core-documentation"><img src="https://agentmods.dev/badge/skills/derailed-dash/dazbo-agent-skills/maintaining-core-documentation/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/skills/derailed-dash/dazbo-agent-skills/maintaining-core-documentation"><img src="https://agentmods.dev/badge/skills/derailed-dash/dazbo-agent-skills/maintaining-core-documentation.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.00059 | $0.02678 |
| Opus 5 | $0.00030 | $0.01339 |
| Sonnet 5 | $0.00012 | $0.00536 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
maintaining-core-documentation scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
* **Key Sections**: Scope (e.g. Python, frontend, agents), tooling (pytest, ruff, etc.), CI/CD environment specifics (Local vs `CI=true`), Unit/Integration/E2E test descriptions, Manual verification steps (e.g., `curl` s How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining Core Documentation
This skill provides a comprehensive framework for the creation and maintenance of high-quality, professional technical documentation for any software project or repository.
Table of Contents
- Triggers
- Mandatory Initialization
- Core Principles
- Technical Writer Skill Synergy
- Document Maintenance Guide
- Formatting Rules
- Documentation Review Process
Triggers
This skill should be triggered whenever:
- The user requests to create or review documentation.
- The user adds / changes / deletes functionality, or makes significant changes to the codebase.
- The user makes any changes to testing.
- The user makes any changes to deployment.
Mandatory Initialization
Before performing ANY documentation task, you MUST check for the presence of the technical-writer skill, by following the guidance in the Technical Writer Skill Synergy section below.
Core Principles
- Persona & Style: Maintain a tone that is professional ("Expert Architect"), technical but welcoming. Use a high-level architectural perspective when explaining the "Why" behind design decisions.
- Cross-Document Synchronisation: Changes to a core property (like a project ID, a URL, or a file path) must be propagated to all applicable documentation files immediately.
- Read Existing Documentation: Always read the existing documentation files to understand the current state and intent of the project.
- Tech Stack: If the file
conductor/tech-stack.mdis present, read it to understand the intended tech stack. - Technical Accuracy: Do not assume that the existing documentation is accurate or up-to-date. Verify the codebase, configuration settings (e.g.
config.py,Makefile,*.tfvars,pyproject.toml), environment variable names, and command flags, before updating documentation. - Ask About Unknowns:
- Ask questions to help establish design choices and technology selection.
- Ask questions to help establish the rationale for any design decisions that are missing rationale.
- Technical Writer Synergy: When performing documentation maintenance, you MUST make use of the
technical-writerskill IF (and only IF) thetechnical-writerskill is present. If it is not found, follow the Technical Writer Skill Synergy section below.
What ships with it
12 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.
- references/architecture-and-walkthrough.md.template 838 B
- references/deployment-README.md.template 615 B
- references/design.md.template 1.8 KB
- references/README.md.template 3.0 KB
- references/samples/deployment/README.md 8.6 KB
- references/samples/docs/architecture-and-walkthrough.md 31 KB
- references/samples/docs/DESIGN-exemplar-swiss.md 3.2 KB
- references/samples/docs/DESIGN.md 4.1 KB
- references/samples/docs/testing.md 11 KB
- references/samples/README.md 10 KB
- references/testing.md.template 536 B
- references/TODO.md.template 121 B
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.
- 11d ago First seen · 188 lines · 59 tokens per session scan A c27312d34bfd
maintaining-core-documentation is a skill published in the GitHub repository derailed-dash/dazbo-agent-skills (24 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,678 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
learning-quality
Structured format for capturing high-quality learnings during ClosedLoop runs.
plan-validate
Deterministic plan.json validation via Python script, replacing most plan-validator agent calls. Performs JSON parsing, schema validation, task checkbox regex, required section checks, sync validation, and data extraction. Only semantic consistency checks (storage/query alignment) require the LLM agent. Triggers on…
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
Presentations
Read, create or edit PowerPoint or Google Slides decks. Use for presentation, slide deck, PowerPoint, PPT, PPTX, or Google Slides requests.
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
intuitive-refactor
Refactor and cleanup router for known code/module/API seams, stale surfaces, compatibility shims, architecture cleanup targets, changed-code quality review, oversized modules, repeated cleanup campaigns, and recurring whole-repo architecture maintenance goals. Use this when the user names a concrete seam, wants…