phira-impl-vs-claim-audit

phira-impl-vs-claim-audit is a skill for Claude Code, Codex from phira-ai/Phira. It costs 34 tokens per session (676 once invoked), scanned A, original, GPL-3.0.

A procedure for checking whether a document accurately describes an implementation, including its default settings.

In plain words
What is it for?
Use it to review algorithm descriptions, technical papers, and implementation documentation against source code and defaults.
Why use it?
It helps find differences between what the code actually does and what the documentation claims.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to review algorithm descriptions, technical papers, and implementation documentation against source code and defaults.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/phira-ai/phira/phira-impl-vs-claim-audit
Install

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.

Any agent
npx skills add phira-ai/Phira --skill phira-impl-vs-claim-audit
Clone the repo
git clone --depth 1 https://github.com/phira-ai/Phira

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for phira-impl-vs-claim-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/phira-ai/phira/phira-impl-vs-claim-audit/github.svg)](https://agentmods.dev/skills/phira-ai/phira/phira-impl-vs-claim-audit)
Your own site
<a href="https://agentmods.dev/skills/phira-ai/phira/phira-impl-vs-claim-audit"><img src="https://agentmods.dev/badge/skills/phira-ai/phira/phira-impl-vs-claim-audit/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.

agentmods 80×15 button for phira-impl-vs-claim-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/phira-ai/phira/phira-impl-vs-claim-audit"><img src="https://agentmods.dev/badge/skills/phira-ai/phira/phira-impl-vs-claim-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 676 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00676
Opus 5 $0.00017 $0.00338
Sonnet 5 $0.00007 $0.00135
Haiku 4.5 $0.00003 $0.00068

Measured 11d ago against content hash 04cfa87c918d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

phira-impl-vs-claim-audit 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 11d 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.

skills/phira-impl-vs-claim-audit/SKILL.md · 71 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 11d ago First seen · 71 lines · 34 tokens per session scan A 04cfa87c918d

Subscribe to this mod's changes

phira-impl-vs-claim-audit is a skill published in the GitHub repository phira-ai/Phira (10 stars, last pushed 6mo ago), licensed GPL-3.0. It adds 34 tokens to every session and 676 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-31.

Related

Other skills, from other repositories

paper-summarizer

Agents should invoke this skill for academic or technical papers, arXiv/PubMed/IEEE/ACM links, PDFs, methodology review, limitations, practical implications, or extracting findings for engineering decisions.

waybarrios/opencode-power-pack · 46 tokens

review-export

Export CocoReview reports as markdown, html, or pdf-ready status artifacts. Usage: $review export markdown|html|pdf [report-path].

Snowflake-Labs/cocoplus · 32 tokens

doc-drift

Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…

AlexZio00/sovereign-skills · 240 tokens

docs-sync-internal

Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…

The01Geek/prflow · 105 tokens

adversarial-document-reviewer

Conditional document-review persona, selected when the document has >5 requirements or implementation units, makes significant architectural decisions, covers high-stakes domains, or proposes new abstractions. Challenges premises, surfaces unstated assumptions, and stress-tests decisions rather than evaluating…

udecode/plate · 59 tokens

firewall-review

Evidence-safe firewall ruleset audit reference specification — 22 documented detector patterns (17 vendor-agnostic plus 5 FortiGate-specific), a 15-check semantic catalogue, CIS Fortinet FortiGate Benchmark guidance, a custom customer-policy benchmark, and consolidated network-team Excel profiles including grouped…

transilienceai/communitytools · 100 tokens