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 iusztinpaul/squid --skill squid-triage-issuegit clone --depth 1 https://github.com/iusztinpaul/squidWrote 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/iusztinpaul/squid/squid-triage-issue)<a href="https://agentmods.dev/skills/iusztinpaul/squid/squid-triage-issue"><img src="https://agentmods.dev/badge/skills/iusztinpaul/squid/squid-triage-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/iusztinpaul/squid/squid-triage-issue"><img src="https://agentmods.dev/badge/skills/iusztinpaul/squid/squid-triage-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 111 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00050 | $0.02039 |
| Opus 5 | $0.00025 | $0.01019 |
| Sonnet 5 | $0.00010 | $0.00408 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
squid-triage-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 3d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage — turn a bug report into a groomed, fixable task
/squid-implement-task and /squid-implement-night both assume the spec is already shaped right. Bug reports rarely are: they read "X is broken" and need a reproducer, expected-vs-actual, code localisation, and a regression-test acceptance criterion before SWE / Tester can do anything useful with them. This skill produces that groomed bug task, then hands off.
You are the triage orchestrator — you may delegate exploration to sub-agents (Explore, general-purpose), but you do NOT write production code, do NOT write the regression test, and do NOT start the fix. Your output is the spec.
$ARGUMENTS is one of:
- A free-form bug description (paste-in customer report, stack trace, "X is broken when Y").
- A path to a markdown report (
docs/bugs/foo.md). - A tracker reference (
NNN-slugin file mode,#Nin gh mode).
If empty, ask the user for one before proceeding.
Read AGENTS.md first to confirm the active tracker mode (file or gh).
When NOT to use
- A feature request — use
/squid-plan(PA grooming) directly. - A refactor with no observable user impact — use
/squid-refactor. - A trivial typo or one-line bug you can fix right now in chat — just fix it.
- An incident still in progress — stabilise first, triage after.
Step 1 — Resolve the report
Identify what to triage from $ARGUMENTS:
- File path →
catthe report. - Tracker reference (
NNN-slugfile mode,#Ngh mode) → load the existing record (tasks/NNN-*.mdorgh issue view N --json number,title,body,labels). - Free-form text → use as-is.
- Empty → ask: "What bug should I triage? (Paste the report, give me a path, or a tracker reference.)"
Echo the resolved report back to the user in one paragraph as confirmation. Don't block — proceed.
Step 2 — Localise
Spawn ONE Explore agent (or general-purpose if the report is vague enough that exploration needs interview-style breadth). Prompt sketch (adapt as needed):
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.
- 3d ago Changed · -21 lines f0551018a4db
- 9d ago First seen · 207 lines · 50 tokens per session scan A 9dadd918486a
squid-triage-issue is a skill published in the GitHub repository iusztinpaul/squid (186 stars, last pushed 5d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,039 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-30.
Other skills, from other repositories
triage-issue
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.
qa-investigation
Investigate a specific test failure to its root cause and document the why. Detects whether a failing test is flaky (intermittent) or a deterministic bug during reproduction. Use when a test fails and you need the real cause, not just to make it green. Execution layer, not strategy review. Keywords: flaky test…
diagnose
A disciplined workflow for investigating software that behaves incorrectly, crashes, produces wrong output, or fails intermittently. It first requires a repeatable command that can demonstrate the reported problem before testing possible causes.
legacy
Legacy code modernization skill. Characterization tests, golden master, incremental modernization, dependency upgrades, dead code removal. Triggers on: /godmode:legacy, "legacy code", "modernize", "tech debt", "dead code".
scenario
Edge case exploration. 12 dimensions, scored by likelihood x impact. Runnable tests for HIGH+.
triage-issue
Invoked helper skill for deep bug diagnosis, usually delegated from /qa when a reported issue needs root-cause analysis and a TDD fix plan before implementation. Use when the cause is unclear, the bug is a regression, or the user explicitly wants diagnosis. Not for lightweight QA intake (use /qa) or already-clear…