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 Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill bug-bounty-triagegit clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-ProtocolWrote 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/samurai-goose/specter-the-illusive-security-protocol/bug-bounty-triage)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/bug-bounty-triage"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/bug-bounty-triage/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/samurai-goose/specter-the-illusive-security-protocol/bug-bounty-triage"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/bug-bounty-triage.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.00040 | $0.01679 |
| Opus 5 | $0.00020 | $0.00839 |
| Sonnet 5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
bug-bounty-triage 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 11d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Bounty Triage
Purpose
Process raw security findings through structured triage: validate scope, deduplicate, assign severity and confidence, prioritize, and prepare for detailed investigation or reporting. Acts as the central intake funnel for all identified issues.
Triggers
- New potential vulnerability discovered during any assessment
- Batch of scanner results needs processing
- User submits a finding for triage
- Recon data reveals potential attack surface
- Dependency audit or code review produces candidate issues
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
finding_raw |
Raw finding data: description, location, evidence snippet | Yes |
source |
Origin skill or tool that produced the finding | Yes |
existing_findings |
List of already-triaged findings for deduplication | Recommended |
Workflow
-
Scope Check — Verify the finding target is within authorized scope per governance context. Reject out-of-scope findings immediately with documented reason.
-
Intake & Normalize — Parse the raw finding into standard fields:
- Title (concise, descriptive)
- Affected target/files
- Vulnerability type / CWE category
- Raw evidence
-
Deduplication — Compare against existing findings:
- Same vulnerability type + same endpoint = duplicate → merge evidence
- Same vulnerability type + different endpoint = separate finding
- Different vulnerability type + same endpoint = separate finding
- Related findings that chain = link with cross-reference
-
Severity Assessment — Apply
references/severity-matrix.md:- Assign severity (S1–S5) based on impact
- Assign confidence (C1–C4) based on evidence quality
- Consider chaining potential — document if this finding enables escalation
- Mark as Suspected or Confirmed
-
Prioritization — Rank by:
- Severity × Confidence (highest first)
- Exploitability (easy to exploit ranks higher)
- Business impact (user data, financial, reputation)
- Chaining potential
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.
- 11d ago First seen · 173 lines · 40 tokens per session scan A 7d2d9425ade9
bug-bounty-triage is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,679 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…