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/petarzarkov/dunx/docs-passnpx skills add petarzarkov/dunx --skill docs-passgit clone --depth 1 https://github.com/petarzarkov/dunxWrote 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/petarzarkov/dunx/docs-pass)<a href="https://agentmods.dev/skills/petarzarkov/dunx/docs-pass"><img src="https://agentmods.dev/badge/skills/petarzarkov/dunx/docs-pass.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.00065 | $0.01281 |
| Opus 5 | $0.00032 | $0.00641 |
| Sonnet 5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
docs-pass 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docs-pass
One file per invocation. The guard is scripts/no-slop.test.ts; it owns the mode map and the budgets, and this skill is how a file gets under them.
bun test scripts/no-slop.test.ts # names every file, its mode, and what it blew
The rule that does the work
Cut. Do not rewrite. Asking for a rewrite produces different prose at the same length, and the length is the defect. Every pass should shrink the file. A paragraph that survives three deletions and still says the same thing was three sentences long.
Delete outright, without replacement:
- Any sentence that tells the reader what the previous sentence meant.
- Any sentence about the design's virtue rather than its behaviour. Move it to
docs/architecture/if the reasoning is genuinely load bearing, or lose it. - Any restatement of what the code block above already shows.
- Any sentence introducing the next sentence.
Modes
Set by path in the guard's MODES table, first match wins.
| Mode | Holds | Writes |
|---|---|---|
| Tutorial | guide/02-first-steps.md |
One path through, in order, every step runnable. No alternatives, no asides |
| Reference | the rest of guide/, every published README.md |
Signature, behaviour, failure mode. Tables over paragraphs. No narrative |
| Explanation | docs/architecture/*, guide/01-introduction.md |
The decision, the alternative, the measurement. This is where reasoning belongs |
A Reference page that wants to explain why links to the Explanation page. It does not explain in place.
Published or repo-only
docs/ holds user documentation and the maintainer's decision record. Only the
first is on the site, and PUBLISHED_REFERENCE in
internal/docs/scripts/generate.ts
is the list.
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.
- 6d ago First seen · 113 lines · 65 tokens per session scan A c884e2b0b7b9
docs-pass is a skill published in the GitHub repository petarzarkov/dunx (21 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,281 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-30.
Other skills, from other repositories
finance-cleanup
Use when the user wants to clean up transactions, fix categories, find missing recurring charges, or do general transaction hygiene in Copilot Money.
finance-pulse
Use when the user asks how they're doing financially, wants a spending check-in, asks about free money or discretionary budget, or says 'pulse'. Read-only — never writes to Copilot Money.
finance-trip
Use when the user wants to track trip expenses, tag travel transactions, find late-posting charges from a trip, or get a trip spending summary. Example: 'tag my Tahiti trip expenses' or 'how much did I spend in Whistler?'.
finance
Use for open-ended financial questions: 'can I afford X?', 'should I buy X?', 'how much can I spend on Y?', or any affordability, budgeting, or financial planning question. Also use when the user asks a financial question that doesn't fit /finance-cleanup, /finance-pulse, or /finance-trip.
nestjs
Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…
amazon-sync
Use when the user wants to reconcile Amazon order history with Copilot Money transactions — categorize purchases, split multi-category orders, and match card refunds. Requires an Amazon order-data export in CSV form.