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/mheraskin/soloe/issue-trackergit clone --depth 1 https://github.com/mheraskin/soloeWhat 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.00068 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
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 yesterday.
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
Issues and PRDs for this repository live in GitHub Issues. Infer the repository from the current
Git remote and use the gh CLI to read or change issues.
Creating or publishing an issue or PRD means creating a GitHub issue. Read an issue with its comments and labels before acting on it.
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.
- yesterday First seen · 8 lines · 0 tokens per session scan A 4f9113ba48ca
issue-tracker is an agent published in the GitHub repository mheraskin/soloe (1 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 68 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-31.
Other agents, from other repositories
executor
The main task execution agent. Spawned for each task in a project. Executes the task described in its prompt — builds, tests, commits, and verifies. Use this when a project task needs to be executed autonomously.
integration-checker
Runs once at the end of a project, after all steps complete. Verifies that all pieces connect correctly across step boundaries — exports used, APIs called, data flows end-to-end. Returns a comprehensive integration report.
verifier
Runs between steps to independently verify the previous step's work. Uses goal-backward verification: checks that the step achieved its GOAL, not just that tasks completed. Three-level artifact verification (exists, substantive, wired). Returns pass/fail verdict with evidence.
spot-checker
Lightweight check that runs between waves. Quickly verifies that files from the completed wave exist and commits are real. Fast gate — not a full review. Uses haiku for speed and cost.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.