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/danhnm1203/scrollytelling/issue-trackergit clone --depth 1 https://github.com/danhnm1203/scrollytellingWhat 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.00247 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| 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
Issues for this repo live in GitHub Issues on danhnm1203/scrollytelling,
managed with the gh CLI.
Skills that read from or write to the tracker (to-tickets, to-spec, triage, qa)
should use gh issue create, gh issue list, and gh issue edit against that repo.
Triage labels
The five canonical roles, each label string equal to its name:
| Role | Label |
|---|---|
| Needs triage | needs-triage |
| Needs info | needs-info |
| Ready for agent | ready-for-agent |
| Ready for human | ready-for-human |
| Won't fix | wontfix |
Only ready-for-agent and wontfix exist on the repo so far; create the others on
first use.
PRs as a request surface
Off. External pull requests do not enter the triage queue.
Blocking edges
GitHub has no native "blocked by" field, so each issue states its blockers in a
## Blocked by section referencing issue numbers.
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 · 32 lines · 0 tokens per session scan A dbd60a90c070
issue-tracker is an agent published in the GitHub repository danhnm1203/scrollytelling (5 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 247 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
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
frontend-specialist
Frontend UI/UX implementation specialist.
mcp
The page outline agents read for line offsets, the in-browser WebMCP bridge and when to run it yourself, the rate limits, and how the surfaces are tested.
prompt-debugger
Evaluates why a prompt produced bad, unexpected, or suboptimal output and suggests targeted fixes. Use when a user says "my prompt isn't working", "this prompt gives bad results", "why is my prompt failing", "debug this prompt", "the AI keeps getting this wrong", "fix my prompt", "prompt not producing expected…
fastify-reviewer
Reviews Fastify application code for anti-patterns, encapsulation violations, and production readiness issues. Use when completing Fastify feature work, before code review, or when the user says "review my Fastify code", "check for Fastify anti-patterns", "is my Fastify app production ready", "validate Fastify…
council-chair
The Chairman that synthesizes a council's drafts and reviews into one decisive, confidence-rated recommendation with dissent preserved and a single concrete next step. Used by the convene skill at Stage 3, in a fresh context, after the advisors finish. JSON-first, then renders the user-facing markdown report. Not for…