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 arozumenko/sdlc-skills --skill discovery-statusgit clone --depth 1 https://github.com/arozumenko/sdlc-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/arozumenko/sdlc-skills/discovery-status)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/discovery-status"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/discovery-status/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/arozumenko/sdlc-skills/discovery-status"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/discovery-status.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.00169 | $0.02673 |
| Opus 5 | $0.00084 | $0.01337 |
| Sonnet 5 | $0.00034 | $0.00535 |
| Haiku 4.5 | $0.00017 | $0.00267 |
Grade B, and why
discovery-status scanned grade B with 1 finding 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 12d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
never lecture on product method. They know how to do discovery; they need to know what the How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
discovery-status
The pipeline has a skill for every stage, a promotion gate, and an optional tracker. This skill is the map. It answers, in one screen: what state is everything in, what is blocked on whom, and what is the single next action?
Audience calibration: the reader is a senior product professional who is new to this agentic toolchain. Report the state of the pipeline — files, fields, checklist, board — never lecture on product method. They know how to do discovery; they need to know what the pipeline expects next and which skill does it.
Retrieval — read the tree, re-derive the checklist, never fabricate
There is no committed dashboard file and no validator script in this bundle. This skill is fast because it reads a small, well-known set of locations directly and re-derives gate state by applying the promotion checklist (below) as prose — not by calling a script or trusting a cached summary. Read in this order:
docs/discovery/hypotheses/— every hypothesis file, regardless ofstatus:(incubating | promoted | parkedis a frontmatter field, not a folder — read all of them). This is the primary worklist for the scorecard below.docs/discovery/outcomes.md— the ratified-outcome register. Zerostatus: activerows is the single most important fact in the whole report if true (see Workspace-level, below).docs/discovery/problems/,docs/discovery/personas/,docs/discovery/journeys/— for the unconverged-inventory pass (orphans with no child hypothesis).docs/discovery/decisions.md— the append-onlyDEC-NNNlog, to confirm a prioritization ranking or a feasibility call was actually recorded, not just claimed.docs/discovery/evidence/{verifications,research,interviews,learnings}/— to confirm a hypothesis's "verified" claim has a real evidence file behind it, not just an assertion.- The product owner's role memory (
.agents/memory/product-owner/— read via thememoryskill if this project uses a different runtime layout for role memory) — for anything logged about an in-flight dispatch (e.g. "tech-lead dispatched on HYP-004, awaiting feasibility read") that has not yet landed as a file underdocs/discovery/. This is a supplement, not a source of truth — a claim that only lives in memory and never lands indecisions.mdor an evidence file is still open, say so. - The tracker board (adapter), only if configured. Read
.agents/profile.mdfor a tracker note: none configured -> the Board-sync section isn/a (no tracker configured);github/gitlab-> query the board viagh/glab. If the CLI fails (no auth), say so and continue with the docs/discovery/-only state — a partial dashboard beats none.
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.
- 12d ago First seen · 186 lines · 169 tokens per session scan B 4ba4741e5bb8
discovery-status is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed yesterday), licensed MIT. It adds 169 tokens to every session and 2,673 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.