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/spiritledsoftware/caplets/issue-trackergit clone --depth 1 https://github.com/spiritledsoftware/capletsWhat 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.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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.
What it actually says
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues in spiritledsoftware/caplets. Use the gh CLI for all issue operations.
Conventions
- Create an issue:
gh issue create --repo spiritledsoftware/caplets --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --repo spiritledsoftware/caplets --comments, filtering comments byjqand also fetching labels when needed. - List issues:
gh issue list --repo spiritledsoftware/caplets --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --repo spiritledsoftware/caplets --body "..." - Apply / remove labels:
gh issue edit <number> --repo spiritledsoftware/caplets --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --repo spiritledsoftware/caplets --comment "..."
gh can infer the repo from the current clone, but commands in skills should include --repo spiritledsoftware/caplets when practical so worktree location does not change the target repository.
Pull requests as a triage surface
PRs as a request surface: no. (Set to yes if this repo later treats external PRs as feature requests.)
When a skill says "publish to the issue tracker"
Create a GitHub issue in spiritledsoftware/caplets.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --repo spiritledsoftware/caplets --comments.
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 · 27 lines · 0 tokens per session scan A ff73f2eca225
issue-tracker is an agent published in the GitHub repository spiritledsoftware/caplets (14 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 417 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
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
inbox-searcher
Email inbox search specialist, takes in appropriate context for the email and a goal of what to search for. Return the answer to the question.
api-designer
API design, documentation, and contract specialist.
researcher
Reads files and grep'd content, no writes.
det
Deterministic-fixture subagent.