Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/reidemeister94/development-skillsnpx agentmods add skills/reidemeister94/development-skills/align-docsWrote 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/reidemeister94/development-skills/align-docs)<a href="https://agentmods.dev/skills/reidemeister94/development-skills/align-docs"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-skills/align-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/skills/reidemeister94/development-skills/align-docs"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-skills/align-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.00021 | $0.00802 |
| Opus 5.5 | $0.00008 | $0.00321 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
align-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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Align docs
Make existing repository knowledge accurate and easy to find. Continue an active workflow with its current task context and authorization. Without task context, inspect only the entry layer and relevant references. Exclude dependencies, caches, build output, and vendored content.
Entry layer
Preserve or establish the project's shared entry layer:
README.md # Human entry point.
AGENTS.md # Critical facts and scoped rules, under 70 lines.
CLAUDE.md # Exactly @AGENTS.md.
.agents/rules/ # Scoped project rules; .gitkeep if empty.
.claude/rules -> ../.agents/rules
docs/ATLAS.md # Curated knowledge routes.
Inspect these files, manifests, relevant agent memory, and documents affected by the current task. Report conflicts or missing facts before making safe in-scope repairs. A normal run never merges or deletes first-party documents and does not scan unrelated history for archive candidates. Use clean mode for a requested full-corpus cleanup.
Owners and evidence
Give each fact one owner: critical facts in AGENTS, scoped instructions in rules, execution in plans, reasons in chronicles. Keep other useful knowledge in its clearest existing home. Verify implementation claims against code and tests, runtime claims against telemetry, promises against contracts, and decision reasons against chronicles. Report unresolved conflicts instead of choosing an unsupported claim.
Preserve an existing AGENTS file's rules. Edit them only within the task's authorization; do not overwrite it with a template.
Use agents-template.md only when creating or explicitly migrating the file.
Remove a leftover align-docs:principles-customized marker.
Keep personal machine facts in .claude/CLAUDE.md or global Codex instructions.
Ensure .gitignore ignores .claude/CLAUDE.md and AGENTS.override.md.
Capture lasting session facts absent from disk; with no session context, report CAPTURE: NONE.
What ships with it
2 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.
- 1mo ago Changed · +19 lines · -24 tokens per session b90d71b07fc7
- 1mo ago First seen · 53 lines · 45 tokens per session scan A 4eff45c1e330
align-docs is a skill published in the GitHub repository reidemeister94/development-skills (12 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 802 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…
db-audit
Database performance and safety audit. 70+ checks across 13 dimensions (DB1-DB13): query patterns, indexes, schema design, connections, transactions, migrations, caching, query optimization, ORM anti-patterns, observability, data lifecycle, DB security, and migration deployment safety. Code-level checks for all ORMs.…
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
code-audit
Batch audit of production files against CQ1-CQ40 quality gates and CAP1-CAP29 anti-patterns. Tiered output (A/B/C/D), critical gate enforcement, evidence-backed scoring, cross-file pattern analysis, and prioritized execution plan. Flags: zuvo:code-audit all | [path] | [file] | --deep | --quick | --services |…