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 saemihemma/lead-producer-oss --skill workflow-project-discoverygit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-project-discovery)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-project-discovery"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-project-discovery/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/saemihemma/lead-producer-oss/workflow-project-discovery"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-project-discovery.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.00033 | $0.00512 |
| Opus 5 | $0.00016 | $0.00256 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
workflow-project-discovery 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Discovery Workflow
Purpose
Create shared situational awareness before design, implementation, or review work goes wide. Turn a vague or inherited project into a short list of concrete next plays.
Use When
- Repo is inherited, large, or poorly mapped
- User asks for discovery, an R&D pass, or "understand this project first"
- Broad unknowns make direct implementation or review premature
- Major systems, docs, tests, or ownership boundaries are unclear
Do NOT Use When
- Immediate bug investigation is the real task (use
workflow-systematic-debugging) - Architecture decision is already tightly scoped (use
team-architecture-review) - One bounded system needs current-reality orientation more than repo-wide mapping (use
workflow-current-state-capture) - User already has a narrow implementation slice ready to execute
Workflow
- Inspect repo shape: package manifests, framework configs, entry points, directory structure, test infrastructure, CI/CD setup, and active documentation.
- Identify the top unknowns blocking confident execution.
- Separate missing facts from preference or strategy questions.
- Offer 2-3 timeboxed next plays sized to the uncertainty:
- quick audit
- focused architecture or subsystem spike
- broader R&D or discovery pass
- Recommend the smallest play that meaningfully reduces risk.
Default Output
PROJECT DISCOVERY REPORT
========================
Current State: repo shape, major systems, artifact maturity, useful existing signals
Top Unknowns: highest-risk things not yet understood
Options: 2-3 timeboxed plays with what each would clarify
Recommendation: smallest next play worth doing now
Next Step: what to inspect next, what decision to make, or recommended next LP route
Output Discipline
- Default to in-chat output only.
- Do not create durable files unless the user explicitly asks.
- Keep options timeboxed and decision-oriented, not open-ended research wishlists.
Anti-Drift Rules
- Discovery is for reducing uncertainty, not backdoor architecture work.
- Name what already exists before proposing more process.
- Recommend the smallest play that changes the next decision.
- Do not auto-chain into follow-on workflows.
- If a follow-on skill is warranted, recommend it back to LP instead of routing directly.
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 · 54 lines · 33 tokens per session scan A 90cc701ab021
workflow-project-discovery is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 512 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…