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 tomzx/agents --skill discover-problemsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/discover-problems)<a href="https://agentmods.dev/skills/tomzx/agents/discover-problems"><img src="https://agentmods.dev/badge/skills/tomzx/agents/discover-problems/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/tomzx/agents/discover-problems"><img src="https://agentmods.dev/badge/skills/tomzx/agents/discover-problems.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.00032 | $0.00563 |
| Opus 5.5 | $0.00013 | $0.00225 |
| Sonnet 5.5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
discover-problems 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 22d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover Problems
The divergent entry point of the PDLC. Turns vague signals (a metric regression, recurring complaints, interview notes, support tickets, a hunch) into structured, solution-agnostic problem statements. Stays strictly in problem space: it refuses to propose solutions.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - A signal source: interviews, tickets, usage data, a metric regression, or a stated concern.
Steps
- Establish or locate the initiative directory under
.pdlc/initiatives/. If none exists, createN-<slug>(issue number if known, else nextp<seq>). - Gather the raw signals. Where interviews exist, extract jobs-to-be-done (the progress a customer is trying to make, their situation, and the forces holding them back). Where data exists, describe the symptom precisely.
- For each candidate problem, write a problem statement in the form: For [who], [current situation/struggle], because [root forces], which results in [measurable harm].
- Rank problems by frequency, intensity, and willingness-to-pay signals.
Mark each as
observed(evidence-backed) vsassumed(hypothesis). - Capture who experiences the problem and how (stakeholders table).
- Record the cost of inaction: what breaks or worsens today, existing workarounds, and the trend (growing / stable / declining).
- Write
problems.mdto the initiative directory using the template.
Output Format
Use the template at skills/pdlc/templates/initiatives/problems.md.
Frontmatter:
---
initiative: INIT-N
title: "<topic>"
status: draft
phase: discover
---
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted and a one-line reason.
Completion Checklist
- Each problem stated without naming a solution
- Each problem marked
observedorassumed - Stakeholders and cost-of-inaction captured
- At least one problem has a frequency/intensity signal (even if weak)
Next Step
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.
- 22d ago Changed · +7 lines e625b91180b2
- 24d ago Changed be2d5bb64bc0
- 1mo ago First seen · 53 lines · 32 tokens per session scan A 5b881e11a9c7
discover-problems is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 563 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.