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 Aboudjem/sniff --skill sniff-reportgit clone --depth 1 https://github.com/Aboudjem/sniffWrote 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/aboudjem/sniff/sniff-report)<a href="https://agentmods.dev/skills/aboudjem/sniff/sniff-report"><img src="https://agentmods.dev/badge/skills/aboudjem/sniff/sniff-report.svg" alt="Measured on agentmods" 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.00013 | $0.00358 |
| Opus 5 | $0.00006 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
sniff-report 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.
What it actually says
/sniff-report - Show last scan results
Display findings from the most recent scan.
This skill is invoked by the sniff skill's own flow, not on its own. The user-invocable: false frontmatter key is honored by Claude Code only, so in other agents this file may show up as a standalone command; treat it as a step inside a sniff run rather than an entry point.
What to do
-
Use the unified
sniffMCP tool with:mode:"report"rootDir: the current project's absolute pathformat: 'summary' for readable output, 'json' for raw data
-
If the unified
snifftool is not available, use legacysniff_reportwith the same rootDir and format. -
Present the summary to the user:
- Total findings by severity
- Top issues with file locations
- Any corroborated findings (confirmed in source + browser)
Example
User: /sniff-report
You: Here are the results from your last scan:
**Summary:** 12 findings (1 critical, 3 high, 6 medium, 2 low)
**Top issues:**
1. `src/routes.ts:14` - CRITICAL: Hardcoded API key
2. `src/handler.ts:42` - HIGH: debugger statement
3. `README.md:28` - HIGH: Broken internal link
Reports saved to:
- .sniff/reports/report.html
- .sniff/reports/report.json
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 · +2 lines 65b316a7e560
- 7d ago First seen · 42 lines · 13 tokens per session scan A aec8077ba011
sniff-report is a skill published in the GitHub repository Aboudjem/sniff (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 358 once invoked, about $0.0001 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
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
lastest
Run visual regression tests, review screenshot diffs, and manage baselines on a Lastest instance via the @lastest/mcp-server MCP tools.
playwright-e2e-testing
Production-grade Playwright end-to-end testing skill for AI coding agents. Provides specialized guidance for writing, debugging, and maintaining Playwright tests in TypeScript, JavaScript, and Python. Covers the full testing lifecycle: test structure and architecture (Page Object Model, fixtures, custom matchers)…
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…