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/fabkho/the-i18n-kit/issue-trackergit clone --depth 1 https://github.com/fabkho/the-i18n-kitWrote 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/agents/fabkho/the-i18n-kit/issue-tracker)<a href="https://agentmods.dev/agents/fabkho/the-i18n-kit/issue-tracker"><img src="https://agentmods.dev/badge/agents/fabkho/the-i18n-kit/issue-tracker.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.00000 | $0.00179 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
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 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
Issue tracker
Specs and issues for this project live in GitHub Issues on
fabkho/the-i18n-kit, managed with the gh CLI.
Creating a spec
gh issue create --title "<title>" --label "ready-for-agent" --body-file <file>
Add a topical label alongside ready-for-agent where one fits
(documentation, enhancement, bug).
Labels
| Label | Meaning |
|---|---|
ready-for-agent |
Spec is complete; an agent can pick this up. No further triage needed. |
documentation |
Docs and reference material. |
enhancement |
New capability. |
bug |
Defect in existing behaviour. |
Do not use the local .scratch/ markdown tracker for this project.
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 · 25 lines · 0 tokens per session scan A 4a936891a310
issue-tracker is an agent published in the GitHub repository fabkho/the-i18n-kit (11 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 179 tokens. 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 agents, from other repositories
worker-executor
Execute pre-approved mutations — Jira transitions, Linear updates, API calls, build commands.
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
planr-worker
Settles one canonical Planr outcome work packet with replayable evidence. Dispatch with the outcome item id.
td-hype-synthesizer
You read every 01scout.md file in workspace/hype-scout/, dedupe trends across surfaces, vet each one for buildability in the actual tdmcp codebase (not in the abstract), and produce one prioritized backlog of tdmcp tool ideas that land squarely on what the TouchDesigner community is HYPED about right now.
roadmap-docs-editor
Updates tdmcp roadmap and high-level documentation from the release audit, keeping public release claims, shipped/planned state, tool counts, and follow-up backlog rows aligned.