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 skills/aretw0/agents-lab/reality-checknpx skills add aretw0/agents-lab --skill reality-checkgit clone --depth 1 https://github.com/aretw0/agents-labWrote 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/aretw0/agents-lab/reality-check)<a href="https://agentmods.dev/skills/aretw0/agents-lab/reality-check"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/reality-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.1 | $0.00040 | $0.00661 |
| Opus 5 | $0.00020 | $0.00331 |
| Sonnet 5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
reality-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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reality-check
Use esta skill antes de transformar uma ideia em gate, primitiva, arena, política de roteamento, mudança de package manager, worker capability ou decisão de governança.
A meta é evitar desenho no vácuo sem virar burocracia. Para fatias triviais, registre apenas uma nota curta. Para decisões que afetam usuários, segurança, providers, workers ou publicação, produza um pacote explícito.
Contrato mínimo
decision:
subject: <o que está sendo decidido>
scope: local-safe | protected | distributed | release
recommendation: adopt | adapt | reject | defer
evidence:
external_or_cached_sources:
- <url, documento local, changelog, issue, paper, benchmark ou runbook>
local_artifacts:
- <arquivo, teste, pacote ou workflow local comparado>
unsupported_hypotheses:
- <hipótese que ainda não tem evidência>
comparison:
adopt:
- <o que usar como está>
adapt:
- <o que usar com ajuste local>
reject:
- <o que não trazer e por quê>
checks:
license: pass | warn | fail | not-applicable
security: pass | warn | fail | not-applicable
budget: pass | warn | fail | not-applicable
governance: pass | warn | fail | not-applicable
next_step:
smallest_safe_slice: <próxima fatia testável>
validation: <smoke, marker-check, dry-run ou leitura bounded>
Regras
- Preferir fontes oficiais, changelogs, issues, benchmarks, runbooks ou evidência cached já presente no repositório.
- Não usar “o modelo sabe” como fonte.
- Se não houver fonte externa ou cached, marcar como hipótese e reduzir a promoção.
- Comparar com artefatos locais antes de recomendar adoção.
- Separar
adopt,adapt,rejectedefer; não esconder tradeoff em texto solto. - Não alterar settings, roteamento, provider defaults, package manager, CI/publish ou escopo protected como efeito da checagem.
- Não fazer chamadas remotas quando a tarefa só precisa de evidência cached/local; quando pesquisa remota for necessária, pedir autorização e citar fontes.
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.
- 6d ago First seen · 72 lines · 40 tokens per session scan A 963777d53725
reality-check is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 661 once invoked, about $0.0002 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
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.
merge-upstream
Sync a fork branch with an upstream remote using a history-preserving merge. Use this whenever the user says /merge-upstream, merge upstream, sync upstream, sync fork, or wants upstream changes integrated without rebasing or force-pushing.
gpt-image-gen
MUST read before generating images. Detailed prompt-crafting guide for gpt-image models, covering tool routing (native imagegeneration server tool vs the generateimage tool), prompt structure from subject to background, verbatim text rendering, anti-patterns, and the revisedprompt feedback loop for iteration.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-primitive-check
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.