Borrowing it
Nothing to install: this file belongs to Pattyboi101/indiestack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pattyboi101/indiestack/master/.agents/skills/fact-check/SKILL.mdgit clone --depth 1 https://github.com/Pattyboi101/indiestackWrote 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/pattyboi101/indiestack/fact-check)<a href="https://agentmods.dev/skills/pattyboi101/indiestack/fact-check"><img src="https://agentmods.dev/badge/skills/pattyboi101/indiestack/fact-check/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/pattyboi101/indiestack/fact-check"><img src="https://agentmods.dev/badge/skills/pattyboi101/indiestack/fact-check.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.00018 | $0.01128 |
| Opus 5 | $0.00009 | $0.00564 |
| Sonnet 5 | $0.00004 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
fact-check 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 9d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact-Check Ed's Email
Ed (co-founder) uses an AI assistant that frequently hallucinates. Your job is to verify every factual claim in his email against the actual IndieStack codebase.
Input
The email text is provided in $ARGUMENTS. If empty, stop and ask for the email text.
Email Text
$ARGUMENTS
Procedure
Step 1: Extract Claims
Read the email carefully and extract every factual claim that can be checked against code. Categories include:
- File paths: Any mention of a file or directory (e.g., "src/indiestack/routes/foo.py")
- Feature status: Claims that something is "done", "pending", "broken", "not yet built", "needs work"
- Route names: URL paths like /explore, /api/something, /dashboard
- Script names: References to Python scripts, shell scripts, CLI commands
- Database fields/tables: Column names, table names, schema details
- Deployment status: Claims about what's live, what's on Fly, environment variables
- Function/class names: References to specific code symbols
- Configuration: Claims about settings, environment variables, dependencies
- URLs: External URLs, API endpoints, webhook paths
- Marketing/content: Claims about content in marketing/ or other docs
Number each claim for the truth table.
Step 2: Verify Each Claim
For each extracted claim, search the codebase methodically:
Key locations to check:
- Routes:
src/indiestack/routes/*.py - DB schema and queries:
src/indiestack/db.py - Main app wiring:
src/indiestack/main.py - Auth:
src/indiestack/auth.py - Payments:
src/indiestack/payments.py - Email:
src/indiestack/email.py - MCP server:
src/indiestack/mcp_server.py - Root-level scripts:
/home/patty/indiestack/*.py - Scripts directory:
/home/patty/indiestack/scripts/ - Marketing docs:
/home/patty/indiestack/marketing/*.md - Static assets:
src/indiestack/static/ - Config:
pyproject.toml,fly.toml,Dockerfile,server.json - Architecture doc:
/home/patty/indiestack/ARCHITECTURE.md
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.
- 9d ago First seen · 122 lines · 18 tokens per session scan A 6860428eea23
fact-check is a skill published in the GitHub repository Pattyboi101/indiestack (4 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,128 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…