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 Cratis/AI --skill cratis-engineering-issue-hygienegit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-engineering-issue-hygiene)<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-issue-hygiene"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-issue-hygiene/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/cratis/ai/cratis-engineering-issue-hygiene"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-issue-hygiene.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.00041 | $0.02210 |
| Opus 5.5 | $0.00016 | $0.00884 |
| Sonnet 5.5 | $0.00008 | $0.00442 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
cratis-engineering-issue-hygiene 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 3d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Leave fewer issues, with a truthful description
An issue must make sense to a reader outside the session. Keep its present state in the description and meaningful events in the timeline. Before any mutation, read capability-is-not-authority.md. The request authorizes its named effects, not arbitrary filing or closing.
One writer and a clear claim
One person or session owns all body edits, comments and disposition for a named issue. Delegated workers report findings to that owner. An explicit handoff can transfer the named issue, but the previous writer must stop editing it. GitHub body edits are not conditional writes; a last-minute reread alone cannot prevent two writers from overwriting each other.
Before starting, read the issue, comments, assignees and any status block. Follow issue-assignment.md and this claiming procedure:
- Applies when the user, branch, task or handover names an issue number in a known repository. No known repository or issue means no guessed assignment.
- Read assignees and state in that issue's repository:
gh issue view <n> --repo <owner>/<repo> --json assignees,state. - If open and unassigned, run
gh issue edit <n> --repo <owner>/<repo> --add-assignee @me.@memeans the authenticated user, not an invented identity. - Never replace or add to an existing assignment. Skip a closed issue; say so without reopening or assigning it.
- Do this once, at the start before the first edit, not on every turn. If it fails (permissions or authentication), report it and continue with the work.
The request to work on the issue authorizes this assignment only, not comments, labels or closure. If another writer is active, coordinate rather than starting a parallel edit. Delegated workers do not claim or mutate the issue.
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.
- 3d ago Changed · -70 tokens per session b8e2310f1d1c
- 4d ago Changed · +14 lines 6cbada5a3dc6
- 5d ago First seen · 185 lines · 111 tokens per session scan A b52e3b8bf00c
cratis-engineering-issue-hygiene is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,210 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-10-25.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…