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 darellchua2/opencode-config-template --skill srs-creation-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/srs-creation-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/srs-creation-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/srs-creation-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.03330 |
| Opus 5 | $0.00026 | $0.01665 |
| Sonnet 5 | $0.00010 | $0.00666 |
| Haiku 4.5 | $0.00005 | $0.00333 |
Grade A, and why
srs-creation-skill 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide a structured Software Requirements Specification (SRS) creation workflow following the IEEE 830 standard — the recognized BA-to-developer requirements document. The SRS is an internal document (audience = development team), distinct from the customer-facing Vision Document.
- IEEE 830 SRS Template — 4-part structure (Introduction / Overall Description / Specific Requirements / Supporting Information) preserving the valuable sections of the prior PRD template (acceptance criteria, NFRs, MoSCoW priorities, risks) by mapping them into the IEEE structure
- docs/srs/ Naming Convention — draft files (
SRS-draft-{slug}.md) renamed to ticket-keyed files (SRS-{key}.md) after ticket creation - PLAN Back-Linkage — bidirectional traceability between SRS and PLAN files
- Discovery Interview Workflow — prompt-first flow that gathers content section-by-section with user confirmation
Back-compat: the legacy triggers "create prd", "product requirement", "product requirement document", "product doc", "PRD" route to this SRS skill. PRD was the wrong label for BA→dev handoff; SRS (IEEE 830) is the proper-software-house standard.
When to use me
Use this skill when:
- A feature needs internal requirements engineering for the development team (NOT a customer-facing doc — that is
vision-creation-skill) - Someone says "create srs", "software requirements", "functional spec", "feature spec", "specification", "write srs"
- You want a structured artifact that feeds into the PLAN file via
ticket-plan-workflow-skill - The customer-facing Vision is signed off and must be translated into developer-ready requirements
- Reviewing/updating an existing SRS
Trigger phrases: "create srs", "software requirements", "functional spec", "feature spec", "specification", "write srs", "srs doc" — plus back-compat "create prd", "product requirement", "product doc", "PRD"
Audience
The SRS is internal — for the development team. It encodes tradeoffs, non-goals, MoSCoW priorities, build-vs-buy rationale, performance targets, and traceability that you would NOT put in front of a customer. The customer-facing equivalent is the Vision Document (vision-creation-skill).
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 First seen · 418 lines · 52 tokens per session scan A 52e6039f355a
srs-creation-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 3,330 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
csv-workbench
Analyze CSV files in /mnt/data and return concise numeric summaries.
pdf-processing
Process and extract information from PDF documents. Use this skill when the user asks to read, analyze, or extract data from PDF files.
data-analysis
DuckDB-powered analytical engine for large data dumps (JSON, CSV, Parquet). Ingest → Profile → Query → File insights.
cite-sources
How to attribute every factual claim to a corpus document.
google-workspace
Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration via gws CLI (googleworkspace/cli). Uses OAuth2 with automatic token refresh via bridge script. Requires gws binary.
notion
Notion API for creating and managing pages, databases, and blocks via curl. Search, create, update, and query Notion workspaces directly from the terminal.