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/zakelfassi/skills-driven-developmentnpx agentmods add skills/zakelfassi/skills-driven-development/manpage-syncWrote 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/zakelfassi/skills-driven-development/manpage-sync)<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/manpage-sync"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/manpage-sync/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/zakelfassi/skills-driven-development/manpage-sync"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/manpage-sync.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.00060 | $0.00887 |
| Opus 5.5 | $0.00024 | $0.00355 |
| Sonnet 5.5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
manpage-sync 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manpage Sync
Regenerate man pages and shell completion scripts to match the current command tree.
Inputs
- Scope:
all(default),man, orcompletions - Output directory for man pages (defaults to
docs/man/) - Output directory for completions (defaults to
completions/)
Steps
-
Build the latest binary
cargo build --release # or: go build -o dist/shipctl ./cmd/shipctlMan page generation requires the actual binary to self-report its command tree.
-
Generate man pages
# Using help2man: help2man --no-discard-stderr ./target/release/shipctl \ -o docs/man/shipctl.1 \ --name "cross-platform deployment CLI" # For each subcommand: help2man --no-discard-stderr "./target/release/shipctl {subcommand}" \ -o "docs/man/shipctl-{subcommand}.1" \ --name "shipctl {subcommand}" # Alternatively, if the binary has built-in man generation: ./target/release/shipctl man --output-dir docs/man/ -
Generate shell completions
./target/release/shipctl completions bash > completions/shipctl.bash ./target/release/shipctl completions zsh > completions/_shipctl ./target/release/shipctl completions fish > completions/shipctl.fish ./target/release/shipctl completions powershell > completions/shipctl.ps1 -
Verify the output
- Run
man -l docs/man/shipctl.1and skim for obvious formatting errors - Spot-check that new flags appear in completions:
grep "{new-flag}" completions/shipctl.bash - Confirm no old flags that were removed still appear
- Run
-
Commit the generated files
git add docs/man/ completions/ git commit -m "docs(manpages): regenerate for $(./target/release/shipctl --version)" -
Update install instructions if a new section or man page was added Edit
docs/install.md→ the "Shell completions" and "Man pages" sections.
Conventions
- Man pages are committed to
docs/man/; they are generated, never hand-edited - Completion scripts are committed to
completions/; same rule - This skill is run in CI after any command-tree change (see
.github/workflows/docs.yml) - Section numbers:
shipctl(1),shipctl-release(1),shipctl-build(1), etc.
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 First seen · 79 lines · 60 tokens per session scan A f3de2f02715b
manpage-sync is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 887 once invoked, about $0.0002 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
code-simplifier
Always-active simplicity rules: no speculative abstractions, one job per function, max 30 lines, flat over nested with early returns, descriptive names, comments explain why.
critical-review
4-phase adversarial review protocol: pre-flight analysis, adversarial execution check, self-correction loop, and [VALIDATION] report.
agent-delegation
Rules for when and how to spawn sub-agents: Explore for 3+ file reads, parallel agents for independent tasks, summaries only — raw output never enters main context.
memory-first
Lookup chain enforced before any file read or search: project and global memory, grep/glob, targeted read — stop at the first step that answers.
verbosity
Response verbosity protocol: reads the level from /.claude/memory/verbosity.md and applies the MIN, INFO or VERBOSE output rules to every reply.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…