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-current-state-capturegit 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-current-state-capture)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-current-state-capture"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-current-state-capture/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-current-state-capture"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-current-state-capture.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.00039 | $0.00622 |
| Opus 5 | $0.00019 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
workflow-current-state-capture 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 10d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current State Capture Workflow
Purpose
Orient a new owner to one bounded system, module, feature flow, or artifact cluster by capturing current reality before change work starts.
Use When
- User needs "I'm new here" understanding for one subsystem or flow
- Code, config, docs, or artifacts exist but the current picture is fragmented
- User wants current behavior, boundaries, and reading order before making changes
- A bounded handoff artifact would reduce repeated rereading
Do NOT Use When
- Broad repo mapping is the real blocker (use
workflow-project-discovery) - Root cause is still unknown and the task is debugging (use
workflow-systematic-debugging) - User needs a fresh architecture decision, not documentation from current reality
- A large documentation set rewrite is already clearly required (use
team-documentation)
Workflow
- Inspect implementation and the tightest set of related docs or artifacts for the target area.
- State what the thing is, what it is not, and where it ends.
- List main moving parts, interfaces, truth sources, constraints, and current behavior.
- Separate confirmed reality from contradictions, gaps, or unresolved areas.
- Give the best reading or inspection order for someone new.
- Recommend the next LP route only if it would materially help.
- If the user wants persistence, save to
_artifacts/current-state-<slug>.md.
Default Output
CURRENT STATE CAPTURE
=====================
Subject: system or module analyzed
What It Is: current responsibility, boundary, and purpose
What It Is NOT: explicit non-goals, neighboring concerns, or rejected interpretations
Moving Parts: key files, components, interfaces, and dependencies
Truth Sources: strongest code, config, docs, or artifacts to trust first
Current Behavior: what the implementation clearly does now
Constraints: important limits, assumptions, or invariants
Known Gaps: stale docs, contradictions, or unresolved questions
Read Next: best inspection order for a new owner
Recommended Next LP Route: follow-on LP route if needed, otherwise 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.
- 10d ago First seen · 59 lines · 39 tokens per session scan A 4f8d0950357d
workflow-current-state-capture is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 622 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…