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 agents/get-tmonier/argot/issue-trackergit clone --depth 1 https://github.com/get-tmonier/argotWhat 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.00000 | $0.00199 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
issue-tracker 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 2d 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.
This is a copy
95% identical to issue-tracker — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Issue tracker: Local Markdown
Issues and PRDs for this repo live as markdown files in .scratch/.
Conventions
- One feature per directory:
.scratch/<feature-slug>/ - The PRD is
.scratch/<feature-slug>/PRD.md - Implementation issues are
.scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from01 - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - Comments and conversation history append to the bottom of the file under a
## Commentsheading
When a skill says "publish to the issue tracker"
Create a new file under .scratch/<feature-slug>/ (creating the directory if needed).
When a skill says "fetch the relevant ticket"
Read the file at the referenced path. The user will normally pass the path or the issue number directly.
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.
- 2d ago First seen · 20 lines · 0 tokens per session scan A 9a052f459952
issue-tracker is an agent published in the GitHub repository get-tmonier/argot (48 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 199 tokens. A static security scan graded it A with 0 findings. It is 95% identical to issue-tracker, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
evolve-memo
Lightweight PASS-cycle memo agent (v8.57.0+, Layer P). Fires on PASS verdicts after ship to capture observations Scout/Triage saw but did NOT commit to topn. Single-pass, $0.10–0.20 per cycle. Emits carryover-todos.json and memo.md — does NOT do retrospective/digest work (that's the FAIL/WARN retrospective agent's…
journey-enforcer
You are a journey coverage AUDITOR. You report on coverage gaps, missing journey contracts, and untested user flows. You do NOT enforce test execution -- that is journey-gate's responsibility.
sprint-executor
You are a sprint execution coordinator. You take a dependency map (from dependency-mapper) and orchestrate parallel implementation waves using Claude Code's Task tool. You create tasks with blockedBy relationships, pre-assign collision-prone resources (migration numbers, file paths), launch agents per wave, track…
dependency-mapper
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.
builder-guidance
Decision frameworks for builder-style agents (sprint-executor, migration-builder, frontend-builder, edge-function-builder, etc.) during active implementation work.
harness-doctor
Check a claudeconf-generated harness against its RECORDED constitution profile — advisory, evidence-driven, read-only. Use when the user asks to check, diagnose, or "doctor" their harness, verify pins/wiring/drift, see whether branch protection matches the enforcement checklist, or whether a profile upgrade is…