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/wedow/ticket/claude-mdgit clone --depth 1 https://github.com/wedow/ticketWrote 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/wedow/ticket/claude-md)<a href="https://agentmods.dev/instructions/wedow/ticket/claude-md"><img src="https://agentmods.dev/badge/instructions/wedow/ticket/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.01204 | $0.01204 |
| Opus 5 | $0.00602 | $0.00602 |
| Sonnet 5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
ticket 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 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
See @README.md for usage documentation. Run tk help for command reference. Always update the README.md usage content when adding/changing commands and flags.
Architecture
Core script: Single-file bash implementation (ticket, ~1000 lines). Uses awk for performant bulk operations on large ticket sets.
Key functions:
generate_id()- Creates IDs from directory name prefix + random suffixticket_path()- Resolves partial IDs to full file pathsyaml_field()/update_yaml_field()- YAML frontmatter manipulation via sedcmd_*()- Command handlerscmd_ready(),cmd_blocked(),cmd_ls()- awk-based bulk listing with sorting
Dependencies: bash, sed, awk, find. Optional: ripgrep (faster grep).
Plugin system: Commands can be extended via external executables in PATH.
tk foochecks fortk-foothenticket-fooin PATHtk super foobypasses plugins, runs built-in directly- Plugins receive
TICKETS_DIRandTK_SCRIPTenvironment variables - See
plugins/README.mdfor full conventions
Plugins
Directory Structure
plugins/
├── README.md # Plugin conventions documentation
├── ticket-query # Extracted from core (requires jq)
├── ticket-migrate-beads # Extracted from core (requires jq)
└── ...
pkg/
├── extras.txt # Curated list for ticket-extras meta-package
└── aur/ # PKGBUILD templates
Plugin File Conventions
Plugins in this repo use ticket- prefix (matching the script name). Both tk-* and ticket-* work at runtime.
Required metadata in first 10 lines:
#!/usr/bin/env bash
# tk-plugin: Short description for tk help
# tk-plugin-version: 1.0.0
Extracting Commands to Plugins
When moving a command from core to a plugin:
- Create
plugins/ticket-<name>with the extracted logic - Add metadata comments (
tk-plugin:,tk-plugin-version:) - Remove
cmd_<name>()from core script - Remove from dispatch case statement
- Add
<name>topkg/extras.txt - Update CHANGELOG.md (see below)
- Update README.md usage section
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 · 152 lines · 1,204 tokens per session scan A 8ef3ea72bdfc
ticket CLAUDE.md is an instructions file published in the GitHub repository wedow/ticket (886 stars, last pushed 5mo ago), licensed MIT. It adds 1,204 tokens to every session, about $0.0060 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 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.