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 agentmods add commands/runnithan/claudex-setup/fact-checkgit clone --depth 1 https://github.com/runnithan/claudex-setupWrote 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/commands/runnithan/claudex-setup/fact-check)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/fact-check"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/fact-check.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 | $0.00022 | $0.00169 |
| Opus 5 | $0.00011 | $0.00084 |
| Sonnet 5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
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 4d 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
Review the following content and fact-check every factual claim:
$ARGUMENTS
For each claim:
- Identify the specific factual assertion
- Search the web for verification using authoritative sources
- Classify as Verified, Unverified, or Incorrect
Output a markdown table:
| # | Claim | Status | Source / Notes |
|---|---|---|---|
| 1 | ... | Verified / Unverified / Incorrect | Link or explanation |
After the table, provide a summary: X/Y claims verified, any corrections needed.
If no arguments are provided, ask the user to paste or describe the content they want fact-checked.
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.
- 4d ago First seen · 24 lines · 22 tokens per session scan A 81ce8bf839a9
fact-check is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 169 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 commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.