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 instructions/cosgroveb/debian-packaging-agent-skill/agents-mdgit clone --depth 1 https://github.com/cosgroveb/debian-packaging-agent-skillWrote 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/instructions/cosgroveb/debian-packaging-agent-skill/agents-md)<a href="https://agentmods.dev/instructions/cosgroveb/debian-packaging-agent-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/cosgroveb/debian-packaging-agent-skill/agents-md.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 | $0.00206 | $0.00206 |
| Opus 5 | $0.00103 | $0.00103 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
debian-packaging-agent-skill AGENTS.md 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 4d 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.
What it actually says
generated output
Treat dist/ as CI-owned output.
Edit skills/, doc/, and repo metadata, not generated bundles.
- X run
make distafter source edits and commit the result - O commit source changes only; let CI regenerate
dist/Runmake distonly when the user asks for a local check.
docs
Write user-facing docs for humans, not agents. Cut process-speak, packaging jargon, and internal labels unless the reader needs them. Prefer the concrete label a person would look for on screen or in the repo.
reference documentation
The doc/ directory contains Debian packaging knowledge. These files are the
authoritative reference for the skill. When updating reference docs, preserve the
existing structure and section headings.
workflow
Check repo docs and workflow files before running build or generation commands. Follow the repo's workflow, not generic habits from other projects. If CI owns an artifact, leave it alone unless the user says otherwise.
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.
- 4d ago First seen · 22 lines · 206 tokens per session scan A 76250ee9eabf
debian-packaging-agent-skill AGENTS.md is an instructions file published in the GitHub repository cosgroveb/debian-packaging-agent-skill (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 206 tokens to every session, about $0.0010 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 instructions, from other repositories
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.