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 evidence-and-reportinggit 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/evidence-and-reporting)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/evidence-and-reporting"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/evidence-and-reporting/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/evidence-and-reporting"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/evidence-and-reporting.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.01423 |
| Opus 5 | $0.00020 | $0.00711 |
| Sonnet 5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
evidence-and-reporting 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence & Reporting
Purpose
Transform triaged security findings into structured, professional reports. Ensure all findings have complete evidence, consistent formatting, proper severity classification, and actionable remediation. Generate executive summaries, finding detail sections, and remediation priority lists.
Triggers
- Assessment complete, findings ready for report
- User requests report generation
- Finding batch reaches reporting threshold
- Stakeholder requests status update
- Individual finding needs formal documentation
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
findings |
Triaged findings from bug-bounty-triage |
Yes |
report_type |
full, executive, finding-only, delta |
Default: full |
audience |
technical, executive, mixed |
Default: mixed |
Workflow
-
Validate Findings — For each finding, verify:
- Title is concise and descriptive
- Severity and confidence assigned per
severity-matrix.md - Status clearly marked: Suspected, Confirmed, Remediated, False Positive
- Evidence is present and reproducible
- Affected target precisely identified
- Impact clearly stated
- Remediation is specific and actionable
- Validation notes explain how to verify the fix
- CWE or OWASP category assigned
- No suspected findings presented as confirmed
-
Evidence Quality Check — Each finding must have:
- Proof of concept or clear indicators
- Exact reproduction steps (numbered)
- Relevant request/response data, code snippets, or screenshots
- Timestamps if applicable
- Context: authentication state, user role, environment
- Sensitive data redacted (credentials, PII, real user data)
-
Compile Report — Assemble using
references/report-template.md:Full Report Structure:
- Assessment Summary (scope, dates, authorization)
- Executive Summary (finding counts, risk posture, key themes)
- Methodology (skills used, tools, approach)
- Finding Summary Table (all findings, sortable by severity)
- Detailed Findings (each finding in full template format)
- Remediation Priority (ordered by severity × exploitability)
- Appendices (tool output, raw data, methodology notes)
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.
- 11d ago First seen · 187 lines · 40 tokens per session scan A 19f60c922dea
evidence-and-reporting 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,423 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…