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 Rifteo/skills --skill vuln-diagnosegit clone --depth 1 https://github.com/Rifteo/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/rifteo/skills/vuln-diagnose)<a href="https://agentmods.dev/skills/rifteo/skills/vuln-diagnose"><img src="https://agentmods.dev/badge/skills/rifteo/skills/vuln-diagnose/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/rifteo/skills/vuln-diagnose"><img src="https://agentmods.dev/badge/skills/rifteo/skills/vuln-diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00678 |
| Opus 5 | $0.00032 | $0.00339 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
vuln-diagnose 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Diagnose
A suspected vulnerability is not a finding. Before writing anything, build a deterministic reproduction case. If you cannot reproduce it reliably, you cannot report it.
Inspired by the principle: a fast, deterministic, agent-runnable pass/fail signal is a superpower.
Process
Step 1 — State the Hypothesis
Write one sentence: "I believe [vulnerability type] exists at [endpoint/component] because [observed behaviour]."
This is the claim. Everything that follows either confirms or disproves it.
Step 2 — Build the Feedback Loop
Create the minimal test case that produces a binary YES/NO answer:
- An HTTP request that succeeds when it shouldn't
- A payload that executes when it shouldn't
- A response that contains data it shouldn't
The test must be:
- Reproducible — same result every time
- Minimal — only the essential input, no noise
- Unambiguous — pass is clearly different from fail
If you can't build this test case, the hypothesis is not testable yet. Stop and gather more information.
Step 3 — Test Alternate Explanations
Before confirming, rule out:
- Caching (replay the request — is the result fresh?)
- Rate limiting (does it fail on the 5th attempt?)
- Session dependency (does it work with a fresh session?)
- Race conditions (does it fail on a second run?)
Step 4 — Confirm the Impact
Actually demonstrate the worst-case impact:
- For data access: retrieve data belonging to another user
- For XSS: execute
alert(document.domain)or exfiltrate a cookie - For SQLi: extract a row from a table not intended to be accessible
- For privilege escalation: perform an admin action with a user token
A confirmed impact requires evidence (HTTP request + response, screenshot, extracted data).
Step 5 — Document
Produce a Minimal Reproduction Case:
Vulnerability: [type]
Endpoint: [METHOD] [URL]
Precondition: [e.g., logged in as user A]
Request:
[exact HTTP request]
Response:
[relevant snippet proving the issue]
Confirmed impact: [what was demonstrated]
Reproducible: YES / NO (notes if flaky)
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 · 84 lines · 63 tokens per session scan A 0a4f6982f052
vuln-diagnose is a skill published in the GitHub repository Rifteo/skills (36 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 678 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
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
39-agent-skills-mcp-code-execution
Create a skill that orchestrates the write-execute-analyze loop to autonomously process data. Learn to implement error recovery, iterate toward robust solutions, and test your skill across diverse input scenarios. This is where specification-driven development meets real problem-solving.
endpoint-validator
Deterministic API endpoint validation with pass/fail reporting.
testing-preferred-patterns
Identify and fix testing mistakes: flaky, brittle, over-mocked tests.
dev-branch-deploy
Drive the Hermes/Maia Concourse dev-branch deploy workflow — test stack changes in a live lab before merging to master. Use for "dev branch", "deploy to dev", "hermes-dev-branch", "maia-dev-branch", "test in labs", "dev lane". Covers both the hermes and maia stacks.