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 commands/heurema/reporter/reportgit clone --depth 1 https://github.com/heurema/reporterWhat 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.00051 | $0.01759 |
| Opus 5 | $0.00026 | $0.00879 |
| Sonnet 5 | $0.00010 | $0.00352 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
report 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a helpful issue reporter for heurema products. Your job is to help the user create a well-structured GitHub issue with minimal friction.
Step 1: Detect the heurema product
Run this in bash to detect the current repo:
REMOTE_URL="$(git remote get-url origin 2>/dev/null)"
if echo "$REMOTE_URL" | grep -qE '(github\.com[/:]|^)heurema/'; then
echo "$REMOTE_URL" | sed 's|.*heurema/||; s|\.git$||'
else
echo ""
fi
Save the result as REPO_NAME. If empty or does not contain a heurema repo, try the plugin manifest:
find . -maxdepth 3 -name plugin.json -path '*/.claude-plugin/*' 2>/dev/null | head -1 | xargs cat 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['name'])" 2>/dev/null || echo ""
If that also returns empty, check pyproject.toml:
python3 -c "
import tomllib, pathlib
p = pathlib.Path('pyproject.toml')
if p.exists():
d = tomllib.loads(p.read_text())
print(d.get('project', {}).get('name', ''))
" 2>/dev/null || echo ""
The detected name IS the repo name (heurema repo names match product names).
If still unknown, ask the user: "Which heurema product is this about?" and offer choices:
- mycel
- nex
- jj-supersede
- watchdog-cli
- proofpack
- signum
- delve
- anvil
- herald
- reporter
- skill7.dev
- teams-field-guide
- Other (let them type)
Step 2: Check gh CLI availability
if command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1; then
echo "GH_READY"
else
echo "GH_UNAVAILABLE"
fi
If output is "GH_UNAVAILABLE", note that gh is not available. Continue collecting info — we'll use the fallback path at the end.
Step 3: Ask the user what they want to report
Ask the user to choose:
- Bug Report — Something is broken or behaving unexpectedly
- Feature Request — Suggest a new feature or improvement
- Question — Ask about usage or behavior
If the user passed an argument (e.g., /report bug), skip this step and use the argument.
Step 4: Collect details
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 · 202 lines · 51 tokens per session scan A b6b4b1b9d8f0
report is a command published in the GitHub repository heurema/reporter (1 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,759 once invoked, about $0.0003 per session on Opus 5. 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 commands, from other repositories
oss
Daily OSS contribution check - uses CLI with --json for structured data.
setup-oss
Configure OSS autopilot preferences.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
plan
Show diff between YAML and current GitHub state. No mutations are made.
nyann:hotfix
Create the branch topology for a patch release against a previously tagged version. Ensures release/ . exists from the source tag, then creates hotfix/ off it. After this, the user commits the fix and runs /nyann:release from the hotfix branch.
nyann:ship
Open a GitHub pull request AND merge it in one step. Default uses GitHub's native auto-merge (returns immediately with outcome:"queued"); --client-side polls for green CI in the foreground then runs gh pr merge. Requires gh installed + authed.