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 Pharaoh-so/pharaoh-mcp --skill verifygit clone --depth 1 https://github.com/Pharaoh-so/pharaoh-mcpWrote 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/pharaoh-so/pharaoh-mcp/verify)<a href="https://agentmods.dev/skills/pharaoh-so/pharaoh-mcp/verify"><img src="https://agentmods.dev/badge/skills/pharaoh-so/pharaoh-mcp/verify/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/pharaoh-so/pharaoh-mcp/verify"><img src="https://agentmods.dev/badge/skills/pharaoh-so/pharaoh-mcp/verify.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.00059 | $0.00620 |
| Opus 5.5 | $0.00024 | $0.00248 |
| Sonnet 5.5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
verify 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Claiming work is complete without verification is dishonesty, not efficiency.
Evidence before claims, always.
When to Use
Before ANY claim of success, completion, or correctness. Before committing, creating PRs, moving to next task, or delegating to agents. Applies to every positive statement about work state.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes.
The Gate
- IDENTIFY: what command proves this claim?
- RUN: execute the full command (fresh, in this message)
- READ: full output — check exit code, count failures
- VERIFY: does output confirm the claim?
- ONLY THEN: make the claim
Skip any step and the claim is unverified.
What Counts as Evidence
| Claim | Requires | NOT sufficient |
|---|---|---|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command: exit 0 | Linter passing |
| Bug fixed | Reproduce original symptom: gone | Code changed, assumed fixed |
| Agent completed | Diff shows correct changes | Agent reports "success" |
| Requirements met | Line-by-line checklist verified | Tests passing |
If Pharaoh tools are available, use get_blast_radius on changed functions to confirm every caller is accounted for.
Red Flags — Stop
- Using "should", "probably", "seems to"
- Expressing satisfaction before running verification
- About to commit without fresh test/build/lint output
- Trusting agent success reports without checking
- "Just this once" thinking
- Relying on partial verification
Rationalization Prevention
| Excuse | Reality |
|---|---|
| "Should work now" | Run the command. |
| "I'm confident" | Confidence is not evidence. |
| "Linter passed" | Linter is not the compiler. |
| "Agent said success" | Verify independently. |
| "Partial check is enough" | Partial proves nothing. |
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 · 74 lines · 59 tokens per session scan A 6c6b9051013b
verify is a skill published in the GitHub repository Pharaoh-so/pharaoh-mcp (2 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 620 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
codebase-intelligence
Query the codebase-intelligence CLI to understand TypeScript architecture, dependencies, blast radius, and risk before reading files. Use for any "how is this structured", "what breaks if I change X", "where is the complexity" question.
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.
mandu-mcp-verify
An automatic verification workflow for the Mandu project that runs after edits, generated files, or before a commit. It checks generated behavior, architecture rules, code quality, and project structure in parallel.
test-strategist
This skill should be used when the user asks to "plan test strategy", "improve test coverage", "fix flaky tests", "optimize test performance", or needs guidance on testing infrastructure and quality assurance. Provides expert guidance on test strategy design, coverage analysis, and test quality improvement.
codespaces
Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal…
testatlas
Use for any question about the tests in a .NET test-automation solution (Reqnroll, SpecFlow, NUnit, xUnit, MSTest, Playwright, RestSharp) - finding, identifying, listing or counting the tests, scenarios or step definitions for a feature or keyword, checking whether coverage exists, and before writing, changing or…