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 businesslens/pdd --skill businesslens-verifygit clone --depth 1 https://github.com/businesslens/pddWrote 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/businesslens/pdd/businesslens-verify)<a href="https://agentmods.dev/skills/businesslens/pdd/businesslens-verify"><img src="https://agentmods.dev/badge/skills/businesslens/pdd/businesslens-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/businesslens/pdd/businesslens-verify"><img src="https://agentmods.dev/badge/skills/businesslens/pdd/businesslens-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 110 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 198 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00075 | $0.02275 |
| Opus 5 | $0.00037 | $0.01137 |
| Sonnet 5 | $0.00015 | $0.00455 |
| Haiku 4.5 | $0.00007 | $0.00228 |
Grade A, and why
businesslens-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 4d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify and resolve alignment
Own one invocation from inspection through resolution. The user must not have to invoke map or ideate manually after a finding. Use child agents for bounded phases when the harness supports them; otherwise run the same protocols as internal phase transitions without losing context.
Verification itself is semantically read-only: do not change product meaning or implementation while classifying findings. Approved intent resolution may edit the model. An injected external builder may edit implementation under its own permissions. Re-derive all findings after either mutation.
Read before work:
- references/format.md — model shapes and Reference rules.
- references/verification-rubric.md — inspection, classification, and stopping rules.
- references/build-handoff.md — the required packet for an injected builder.
1. Establish scope and mode
- Require an existing Product Model. If none exists and repository behavior is established, run the scoped-map protocol in step 7 for the necessary scope; do not tell the user to invoke another skill. If both model and implementation are absent, stop: there is nothing to verify.
- Parse mode:
report only→ inspect and report; prohibit every write and delegation;- otherwise → resolution mode.
- Resolve scope:
this branch→ use merge-base, committed, staged, and working-tree diffs only to choose the inspection worklist;currentorfull→ inspect the present modeled product independent of Git history;- named Entity, Interface, Experience, Screen, Domain, Capability, Capability Scenario, Journey, Journey Scenario, Business Rule, availability Context, or path → inspect it and behaviorally necessary dependencies;
- no explicit scope → prefer a reliable changed-surface worklist; when no useful diff exists, inspect the current modeled product.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +14 lines f6b1cd137ce9
- 7d ago Changed · +33 lines be9257fb0d7c
- 12d ago First seen · 166 lines · 75 tokens per session scan A fa67b4cb869a
businesslens-verify is a skill published in the GitHub repository businesslens/pdd (10 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 2,275 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…