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 Rijul1204/rashedul-agentic-engineering --skill srs-to-delivery-plangit clone --depth 1 https://github.com/Rijul1204/rashedul-agentic-engineeringWrote 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/rijul1204/rashedul-agentic-engineering/srs-to-delivery-plan)<a href="https://agentmods.dev/skills/rijul1204/rashedul-agentic-engineering/srs-to-delivery-plan"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/srs-to-delivery-plan/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/rijul1204/rashedul-agentic-engineering/srs-to-delivery-plan"><img src="https://agentmods.dev/badge/skills/rijul1204/rashedul-agentic-engineering/srs-to-delivery-plan.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.00049 | $0.01519 |
| Opus 5 | $0.00024 | $0.00759 |
| Sonnet 5 | $0.00010 | $0.00304 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
srs-to-delivery-plan 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 11d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRS to Delivery Plan
Convert a Software Requirements Specification (SRS) into a structured delivery plan:
SRS → EPICS → STORIES → TASKS → SPRINT PLAN
This system combines:
- Product thinking (EPICS)
- Vertical slicing (STORIES)
- Execution clarity (TASKS)
- Delivery planning (SPRINTS)
Core Principles
Vertical Slice (Tracer Bullet)
Each STORY must:
- Deliver a thin but complete end-to-end flow
- Cut through ALL layers (DB → API → UI → integration → tests)
- Be independently testable and demoable
- Provide real user value
Avoid horizontal slices like:
- "Build database schema"
- "Create API layer"
Instead:
- "User can create account and log in"
HITL vs AFK
HITL (Human-in-the-loop)
Requires:
- Product decisions
- Architecture discussions
- UX validation
AFK
- Can be implemented and merged independently
- No external decision required
Always maximize AFK stories.
PROCESS
Step 1 — Locate the SRS
Ask the user for:
- GitHub issue number OR
- URL OR
- Raw SRS document
If not available → ask for it.
Do NOT proceed without understanding the SRS.
Step 2 — Understand the System
Extract:
- Core features
- User stories
- Key flows
- System boundaries
- Constraints (tech, product, compliance)
Summarize briefly before proceeding.
Step 3 — Create EPICS
Group features into high-level capabilities.
EPIC Rules
- Represents a major deliverable
- Takes ~1–3 weeks
- Contains multiple STORIES
- Focus on outcomes, not implementation
Output Format
For each EPIC:
- Title
- Description
- Covered SRS sections
Step 4 — Create STORIES (Vertical Slices)
Break each EPIC into STORIES.
STORY Rules
- End-to-end functionality
- Demoable independently
- Small (ideally 1–2 days)
- User-value focused
STORY Fields
- Title
- Type: HITL / AFK
- Blocked by
- User stories covered (from SRS)
Step 5 — Create TASKS
Break STORIES into TASKS. Each task must be a self-contained work packet with enough detail that the implementer (human or AI agent) can execute without further clarification.
What ships with it
1 file 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.
- 11d ago First seen · 309 lines · 49 tokens per session scan A a8fe6c718f9a
srs-to-delivery-plan is a skill published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,519 once invoked, about $0.0002 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
ios-app-agentic-engineering
End-to-end agentic engineering for iPhone apps, from idea to a secure App Store release through 8 gated phases. Use when someone wants to build, plan, or ship an iPhone/iOS app — especially a non-programmer ("vibe coder") asking to create an app, pick a tech stack (SwiftUI, React Native, Flutter), choose a backend…
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.