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 SerhiiKorniienko/bullshit-detector --skill report-cardgit clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detectorWrote 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/serhiikorniienko/bullshit-detector/report-card)<a href="https://agentmods.dev/skills/serhiikorniienko/bullshit-detector/report-card"><img src="https://agentmods.dev/badge/skills/serhiikorniienko/bullshit-detector/report-card/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/serhiikorniienko/bullshit-detector/report-card"><img src="https://agentmods.dev/badge/skills/serhiikorniienko/bullshit-detector/report-card.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 80 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00087 | $0.01726 |
| Opus 5 | $0.00044 | $0.00863 |
| Sonnet 5 | $0.00017 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
report-card 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 12d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
report-card
Turn bs-report-<slug>-<date>.md into one HTML file anybody can open.
The markdown is the artifact and stays the artifact — it is what tally.py checks, what gets
diffed against a later run, and what gets committed. This skill adds a reader-facing view of
that same file. It renders; it never edits, recounts, or adds. Every number on the page is copied
from the markdown verbatim.
Why this exists
A BS report is a five-column claims table. On a laptop that is fine. On a phone — which is where a shared link is actually opened — the Evidence column is unreadable, and the reader's first question ("what's wrong with it?") means scrolling twenty rows to find the two that matter.
Usage
uv run <this-skill-dir>/scripts/render_report.py ~/.bullshit-detector/reports/<YYYY>/bs-report-<slug>-<date>.md
Writes bs-report-<slug>-<date>.html beside the markdown. -o <path> puts it elsewhere. No install
step, no dependencies — the script is stdlib-only, runs under plain python3 as well as uv run,
and the page it produces makes no network requests. That combination is what lets it work in a
code-execution sandbox, where the HTML is the only thing the user can take away.
--openshows the page in the default browser. Where there is no browser — a sandbox, a headless host — it says so and the file is still written. It is skipped when the page already exists, because re-rendering is normal (the run line gets finalised after a first pass) and every open spawns another tab — three consecutive real runs left the user with two. The file updates in place; reload the tab you have.--reopenopens even when the page existed — for picking a report back up in a later session. Never treat that as a failure.--quietprints only the output path, for scripting.
The handoff block
By default the script prints the block that ends a detector run:
BS score 4/10 · Mostly fine
the macro data is real and mostly checks out; the narrative glue is crypto-Twitter.
Tally: 35 claims extracted, 34 individually source-checked — 22 confirmed, 5 plausible,
5 misleading, 2 false. 1 not checked.
run: 16m30s, searches 35, tools 65, coverage 1, per claim 29s
markdown file:///Users/…/bs-report-japans-money-is-collapsing-2026-07-31.md
page file:///Users/…/bs-report-japans-money-is-collapsing-2026-07-31.html
opened in your browser
What ships with it
2 files 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.
- 12d ago First seen · 129 lines · 87 tokens per session scan A f8cd0abb3915
report-card is a skill published in the GitHub repository SerhiiKorniienko/bullshit-detector (142 stars, last pushed 9d ago), licensed MIT. It adds 87 tokens to every session and 1,726 once invoked, about $0.0004 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
pdf-design
Designs PDF reports and proposals from HTML with previews and branding. Use to create, export, or securely upload a PDF.
document-design
Creates print-ready HTML that exports to PDF. Use to make a proposal, report, one-pager, newsletter, slides, or flyer.
doj-auth
This skill should be used when the user needs to download or verify a DOJ EFTA PDF, access justice.gov/epstein programmatically, or understand why the DOJ multimedia-search API returns 403 for headless requests. Trigger on: "DOJ blocked", "access denied justice.gov", "download EFTA PDF", "akamai bot", "SHA256 cookie"…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
pdf-extract-create-workflow
Complete PDF lifecycle: download, extract, and generate structured documents with reportlab.