Borrowing it
Nothing to install: this file belongs to joshsmithxrm/power-platform-developer-suite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joshsmithxrm/power-platform-developer-suite/main/.claude/skills/spec-audit/SKILL.mdgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/spec-audit)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/spec-audit"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/spec-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.
<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/spec-audit"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/spec-audit.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.00006 | $0.01205 |
| Opus 5.5 | $0.00002 | $0.00482 |
| Sonnet 5.5 | $0.00001 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
spec-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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Audit
Compare specifications against reality. Find drift, gaps, and undocumented behavior. Produces actionable findings — does not auto-fix.
Input
$ARGUMENTS = spec name for single audit (e.g., connection-pooling), or empty for full audit of all specs
Process
Step 1: Load Foundation
Read these files:
specs/CONSTITUTION.md— principles to check against
Step 2: Determine Scope
Single spec ($ARGUMENTS provided):
- Read
specs/$ARGUMENTS.md - Proceed to Step 3 with this one spec
Full audit ($ARGUMENTS empty):
- Glob
specs/*.md(excluding CONSTITUTION.md, SPEC-TEMPLATE.md, README.md) to get the list of all specs - For each spec, dispatch a parallel subagent (use
Agenttool withsubagent_type: "general-purpose") with the audit prompt below - Collect all results and produce a summary
Step 3: Audit a Single Spec
For each spec, check these categories:
A. Acceptance Criteria Coverage
- Does the spec have an
## Acceptance Criteriasection with numbered IDs? - For each AC that references a test method: does that test file/method exist? (use Grep to search for the method name)
- For each AC with status marked passing: is the status accurate? (run the specific test if possible — .NET:
dotnet test --filter "FullyQualifiedName~{TestMethod}" -v q, TypeScript:npx vitest run -t "{TestMethod}" --prefix src/PPDS.Extension) - Report: verified, test exists but status wrong, test not found, or no AC section
B. Code-to-Spec Alignment
- Read the code files listed in the spec's
Code:header - Check Core Requirements: does each requirement have corresponding code?
- Check Architecture diagram: does the actual code structure match?
- Check Core Types: do the interfaces/classes described still exist with the same signatures?
- Report: matches, drifted (describe how), missing (spec claims but code doesn't have), or extra (code has but spec doesn't describe)
C. Constitution Compliance
- Check the spec's design against each relevant constitution principle
- Focus on: architecture laws (A1-A3) for any spec, Dataverse laws (D1-D4) for Dataverse specs, security laws (S1-S3) for UI specs
- Report: compliant or violation (cite principle and issue)
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.
- 1mo ago First seen · 141 lines · 6 tokens per session scan A c5d2c3d88c32
spec-audit is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 1,205 once invoked, about $0.0000 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-08-31.
Other skills, from other repositories
dynamics365-expert
Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
address-review
Read PR review comments from GitHub, evaluate, address, and reply.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…