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 hectorjarquin/wp-agent-skills --skill wp-requirements-specificationgit clone --depth 1 https://github.com/hectorjarquin/wp-agent-skillsWrote 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/hectorjarquin/wp-agent-skills/wp-requirements-specification)<a href="https://agentmods.dev/skills/hectorjarquin/wp-agent-skills/wp-requirements-specification"><img src="https://agentmods.dev/badge/skills/hectorjarquin/wp-agent-skills/wp-requirements-specification/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/hectorjarquin/wp-agent-skills/wp-requirements-specification"><img src="https://agentmods.dev/badge/skills/hectorjarquin/wp-agent-skills/wp-requirements-specification.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.00115 | $0.02724 |
| Opus 5 | $0.00057 | $0.01362 |
| Sonnet 5 | $0.00023 | $0.00545 |
| Haiku 4.5 | $0.00012 | $0.00272 |
Grade A, and why
wp-requirements-specification 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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
9 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.
- example/feature-slug-srs-default.md 1.5 KB
- example/feature-slug-srs-enterprise.md 1.8 KB
- example/feature-slug-srs-team.md 1.7 KB
- references/brs-template.md 2.9 KB
- references/opscon-template.md 3.7 KB
- references/requirement-quality-criteria.md 9.8 KB
- references/srs-template.md 12 KB
- references/strs-template.md 3.4 KB
- references/syrs-template.md 7.4 KB
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.
- 8d ago First seen · 254 lines · 115 tokens per session scan A 812d44eecf51
wp-requirements-specification is a skill published in the GitHub repository hectorjarquin/wp-agent-skills (2 stars, last pushed 2mo ago), with no licence file. It adds 115 tokens to every session and 2,724 once invoked, about $0.0006 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
project-specification
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
spec-driven-development
Use when starting a new feature or significant change with no spec yet. Covers single-repo and multi-repo features. Do NOT use for typos, single-line fixes, or post-hoc documentation of finished work.
Requirements Clarity & Acceptance Criteria
Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.
spec-linked-docs
Spec-Linked Documentation (SLD): Language-agnostic discipline for maintaining bidirectional traceability between functional specifications and source-code docstrings via stable identifiers and CI validation. Optional/opt-in adoption. Builds on OpenFastTrace and DO-178C Requirements Traceability Matrix traditions.
speckit-specify
Turn a plain feature description into a structured specification (spec.md): overview, user stories, functional and non-functional requirements, and testable acceptance criteria. Trigger on: write a spec, specify this feature, create requirements, spec-driven development, SDD specify.
sparc-spec
Use when you need to run SPARC Phase 1 (Specification) for a feature — produces phase1 .md with Functional Requirements, Non-Functional Requirements, and Gherkin acceptance scenarios.