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/mcinerneyjake/ticket-workflow/claude-mdgit clone --depth 1 https://github.com/mcinerneyjake/ticket-workflowWrote 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/mcinerneyjake/ticket-workflow/claude-md)<a href="https://agentmods.dev/instructions/mcinerneyjake/ticket-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/mcinerneyjake/ticket-workflow/claude-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.01041 | $0.01041 |
| Opus 5 | $0.00521 | $0.00521 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
ticket-workflow CLAUDE.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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket-workflow
This repo follows its own guardrail standard. node dist/cli/index.js audit . (after a build) is the
machine-checkable definition; this file is a pointer to it, not a second copy.
What this package is
The canonical ticket engine: MCP server, guard/telemetry hooks, pipeline CLI (list, show,
doctor, verify, audit, init), the guardrail template set, and the audit that checks any repo
against the standard. Consumers (kanban first) pin it by git tag, never a branch — a fix here
reaches them only through a tag cut plus their own pin bump.
Public and user-agnostic — hard rule
This is a public repo. Never commit a local identifier: no home-directory path naming a real account, no machine-local board paths, no private hostnames.
Enforced in the gate, not by a grep you have to remember. src/repoHygiene.test.ts scans the
index — the snapshot that will actually commit — for ~user/, /Users/user and /home/user,
failing unless the owner is an obvious placeholder (someuser, x, runner, …). The consequence
to know when running it locally: an unstaged edit is not scanned. git add first, or the run
reports on a file you have already changed. src/templates.test.ts holds template contents to the
same standard separately.
This replaced a hand-run git grep with a hardcoded exclusion list, which rotted the worst way: the
list went stale, so it reported a hit on every clean run while the identifier that was actually
committed — a real account name in a ~user/ path — sat in a shape it never matched. A check that
always fires is a check people stop reading (tkt-3a91af2aa6d9).
What it cannot catch. Three gaps, all deliberate and all measured:
- A bare tilde account with no path after it —
cd ~useris invisible, because~wordis ordinary prose (~two hours,~40 lines) and matching it would fire on documentation forever. Only the~user/form is caught. A test pins this so it cannot later be mistaken for coverage. - Anything that is not a path shape. A probe cannot name the identifiers it hunts without committing them, so a bare first name in fixture data is invisible to it.
- Another repo's on-disk directory named in a comment, unless it sits under a home path.
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 First seen · 75 lines · 1,041 tokens per session scan A 9876724a0796
ticket-workflow CLAUDE.md is an instructions file published in the GitHub repository mcinerneyjake/ticket-workflow (0 stars, last pushed yesterday), licensed MIT. It adds 1,041 tokens to every session, about $0.0052 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.