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 skills/seed-hypermedia/seed/report-issuenpx skills add seed-hypermedia/seed --skill report-issuegit clone --depth 1 https://github.com/seed-hypermedia/seedWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/seed-hypermedia/seed/report-issue)<a href="https://agentmods.dev/skills/seed-hypermedia/seed/report-issue"><img src="https://agentmods.dev/badge/skills/seed-hypermedia/seed/report-issue.svg" alt="Measured on agentmods" height="20"></a>What 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.00108 | $0.00912 |
| Opus 5 | $0.00054 | $0.00456 |
| Sonnet 5 | $0.00022 | $0.00182 |
| Haiku 4.5 | $0.00011 | $0.00091 |
Grade A, and why
report-issue 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Creator
Investigate a bug report interactively, then create a clean GitHub issue via the gh CLI.
Prerequisites
Before starting, verify the gh CLI is installed and authenticated:
gh auth status
If not authenticated, tell the user to run gh auth login first and stop.
Also confirm you're inside a git repo with a GitHub remote:
git remote -v
If not, ask the user which repo the issue should be filed against.
Phase 1: Grill the user
Interview the user one question at a time to build a complete picture of the bug. For each question, provide your recommended answer based on what you already know from context or the codebase.
Walk through these areas, but adapt to what's already known — skip questions the user has already answered:
- What happened? — A clear description of the unexpected behavior.
- What was expected? — What should have happened instead.
- Steps to reproduce — The exact sequence to trigger the bug.
- Environment — OS, browser, runtime version, or any relevant env details (only ask if likely relevant).
- Frequency — Does it always happen, or only sometimes? Under what conditions?
- Impact — How severe is this? Does it block anything?
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
Phase 2: Investigate the codebase
Once you understand the bug, dig into the code:
- Find suspects — Search for the code paths most likely involved. Look at recent changes in those areas
(
git log --oneline -10 -- <file>). Summarize what you find for the user. - Propose possible causes — Based on the code, suggest what might be going wrong and why.
- Suggest fixes — If a solution seems clear, describe the approach briefly. This goes into the issue body as context, not as a commitment.
Share your findings with the user and ask if they want to add or correct anything.
Phase 3: Related test scenarios
Before creating the issue, suggest 2-4 related scenarios the user should also verify. These are edge cases or adjacent behaviors that might be affected by the same root cause.
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 · 129 lines · 108 tokens per session scan A 37e8ae78fd4f
report-issue is a skill published in the GitHub repository seed-hypermedia/seed (56 stars, last pushed 2d ago), licensed Apache-2.0. It adds 108 tokens to every session and 912 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…