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 skills add adamlinscott/claude-skills --skill raise-issuegit clone --depth 1 https://github.com/adamlinscott/claude-skillsWrote 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/adamlinscott/claude-skills/raise-issue)<a href="https://agentmods.dev/skills/adamlinscott/claude-skills/raise-issue"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/raise-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adamlinscott/claude-skills/raise-issue"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/raise-issue.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00165 | $0.03939 |
| Opus 5 | $0.00082 | $0.01969 |
| Sonnet 5 | $0.00033 | $0.00788 |
| Haiku 4.5 | $0.00016 | $0.00394 |
Grade A, and why
raise-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 9d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Raise an issue
A good bug report is not a good description. It is a description a developer can act on before they have found the code themselves. That translation is the whole job here.
The person running this skill uses the product. They do not read code, and they should not have to. They will say "the dashboard", "the thing that sends the emails", "the export button spins forever". Your job is to take those words, find what they point at in this repository, confirm the match in plain English, and hand a complete brief to whoever picks the issue up — so nobody has to come back and ask this person a technical question.
Why this skill can be triggered by the model
The omission of disable-model-invocation is deliberate, not an oversight.
The people this skill exists for do not know it exists. They will not type /raise-issue; they
will say "this looks wrong" and wait. Model invocation is the only mechanism that reaches them.
Being model-invocable is not unusual here — most of this collection is. What is unusual is the
blast radius. Every other model-invocable skill in this collection reports, audits, or edits
inside the repo; the worst case is a bad local change the user can undo. This one writes
outside it, to a tracker the whole team reads, under the user's own name, where a mistake is
public and cannot be quietly reverted. /seatbelt carries a comparable weight and answers it the
other way, with explicit invocation only.
So the containment is not the frontmatter. It is step 5: nothing is published, commented on, handed to another skill, or written outside this conversation until a human has read the finished text and said yes. Keep that gate where it is, and keep it ahead of publishing. It is the only thing making auto-invocation safe here, and it is a prose instruction rather than a mechanical lock — so treat it as load-bearing, not as a formality.
Quick start
/raise-issue # asks what went wrong
/raise-issue the export button spins forever # starts from a description
/report-issue # the same skill
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 296 lines · 165 tokens per session scan A 64d3165d5861
raise-issue is a skill published in the GitHub repository adamlinscott/claude-skills (3 stars, last pushed 9d ago), licensed MIT. It adds 165 tokens to every session and 3,939 once invoked, about $0.0008 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
moai-workflow-templates
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating templates, generating boilerplate files, or managing scaffolding.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
workspace-prune-working
Clean up .aiwg/working/ by promoting, archiving, or deleting temporary files.
workspace-realign
Reorganize and update .aiwg/ documentation to reflect current project reality.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.