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/drunkrhin0/antislop/issue-trackergit clone --depth 1 https://github.com/drunkrhin0/antislopWhat 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.00253 |
| Opus 5 | $0.00000 | $0.00127 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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: local Markdown
Specs and tickets for this repository live as Markdown files under .scratch/.
Conventions
- Store each effort under
.scratch/<feature-slug>/. - Store its spec at
.scratch/<feature-slug>/spec.md. - Store one ticket per file under
.scratch/<feature-slug>/issues/NN-<slug>.md. - Number tickets in dependency order.
- Record triage state with a
Status:line near the top of each ticket. - Append discussion under a
## Commentsheading.
Publishing
When a skill says to publish a spec or issue, write the corresponding local file. Do not create a Forgejo or GitHub issue unless the user explicitly changes this configuration.
Wayfinding
- The map is
.scratch/<effort>/map.md. - Child tickets are stored in
.scratch/<effort>/issues/. Blocked by:lists ticket numbers that must be resolved first.- The frontier contains tickets that are open, unblocked, and unclaimed.
- Claim work by changing
Status:toclaimedbefore editing source files. - Resolve work by adding an
## Answer, changingStatus:toresolved, and updating the map.
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 · 26 lines · 0 tokens per session scan A 38865c6df345
issue-tracker is an agent published in the GitHub repository drunkrhin0/antislop (23 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 253 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
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.
pm-workflow-orchestrator
Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
2-generate-tasks
Convert PRDs into development task lists.