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/ronronner02/codepilot-agent/spec-app-consistency-auditgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/spec-app-consistency-audit)<a href="https://agentmods.dev/commands/ronronner02/codepilot-agent/spec-app-consistency-audit"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-app-consistency-audit.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.00009 | $0.04040 |
| Opus 5 | $0.00005 | $0.02020 |
| Sonnet 5 | $0.00002 | $0.00808 |
| Haiku 4.5 | $0.00001 | $0.00404 |
Grade A, and why
spec-app-consistency-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 3d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command support root: .claude/spec-first/workflows/spec-app-consistency-audit. Treat it as the loaded skill directory whenever this inlined workflow refers to SKILL_DIR or the directory containing SKILL.md.
App Consistency Audit
Run a static-first consistency audit for mobile App work before simulator, real-device, or package validation.
Workflow Contract Summary
When To Use
Use when mobile App PRD, Figma context, local source, routes, architecture, analytics, i18n, or industry rules need a static-first consistency audit before runtime validation.
When Not To Use
Do not use for ordinary code review (spec-code-review), PRD authoring or refinement (spec-prd), pure test/lint/build/runtime execution, UI polish (spec-polish), formatting-only changes, or product-source edits.
Inputs
Mode tokens, diff base, source root, PRD/design refs, industry lens, task/tech-plan refs, repository instructions, and app audit extractor facts.
Outputs
Static consistency findings, headless envelopes when requested, degraded-input notes, and report-writer handoff fields.
Artifacts
Headless/default runs may write .spec-first/app-audit/runs/<run-id>/ artifacts; report-only mode writes no run artifacts.
Failure Modes
Conflicting modes, missing headless base, missing or reference-only Figma input, unreadable source/PRD facts, extractor gaps, or insufficient App surface evidence.
Workflow
Resolve mode and scope, collect static product/design/source facts, apply architecture/component/analytics/i18n/industry lenses, synthesize findings, then return or write the requested audit envelope.
Downstream Consumers
移动 QA planning、App implementation owner、report-writer step，以及准备 runtime validation 的人工审查者。
Scenario Capability
Follows docs/contracts/workflows/scenario-capability-matrix.md (default).
Overrides: none
Purpose
Use this workflow to compare product intent, design states, page routes, KMP / Clean Architecture boundaries, App engineering quality, component and module reuse, analytics, i18n, and industry-specific rules from the available local inputs.
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.
- 3d ago First seen · 299 lines · 9 tokens per session scan A bc4dcf979a60
spec-app-consistency-audit is a command published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 4,040 once invoked, about $0.0000 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
Hexagonal.Gatekeeper
Your role is to perform a deep, architecture-focused code review on a specific branch. You must validate that all changes strictly follow Hexagonal Architecture (Ports & Adapters) principles and align with the existing codebase patterns.
Hexagonal.Refactor
Your task is to fix the reported issues in the current branch.
PyTest.GateKeeper
You are a Senior QA Automation Engineer with deep expertise in Python testing and the pytest framework.
review
This command might include optional parameters basic / deep - this is the type of review to invoke if no parameter is given for that option the default should be basic files/folders - if file or folder specification is given only review them.
push
This command will push new design file into the given jira ticket With this command the user will provide arguments.
OPSX: Verify
Verify implementation matches change artifacts before archiving.