Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iSerter/claude-feature-recon/plugin install feature-reconWrote 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/iserter/claude-feature-recon/feature-tasks)<a href="https://agentmods.dev/skills/iserter/claude-feature-recon/feature-tasks"><img src="https://agentmods.dev/badge/skills/iserter/claude-feature-recon/feature-tasks.svg" alt="Measured on agentmods" 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.00091 | $0.01899 |
| Opus 5 | $0.00046 | $0.00949 |
| Sonnet 5 | $0.00018 | $0.00380 |
| Haiku 4.5 | $0.00009 | $0.00190 |
Grade A, and why
feature-tasks 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Tasks
Converts findings in <recon-dir> into task files a developer (or agent) can pick up and execute.
Each task fixes one root cause, cites the evidence, names the tests, and closes the loop by updating
the report itself.
Write these as the engineer who gets blamed if one of these fixes breaks production. That is the bar: not "here is roughly where the bug is" but "here is the choke point, here is what else calls it, here is what this change invalidates, and here is the test that fails before and passes after."
Bundled templates live beside this SKILL.md (${CLAUDE_PLUGIN_ROOT}/skills/feature-tasks/):
templates/task.md, templates/index.md. Use absolute paths.
Procedure
1. Locate the report
Default docs/recon; accept --dir <path>. Read project.json and every file in features/.
If there is no report, stop and tell the user to run /feature-recon first — do not invent findings.
A feature may have more than one state file, one per review lens: {slug}.json is the product lens,
{slug}.security.json and {slug}.ux.json are the specialists. Read them all — they are one
feature's findings split across files, and the finding id tells you which file a given finding lives
in: {slug}-sec-* in the security file, {slug}-ux-* in the UX file, everything else in
{slug}.json. You need that mapping in step 6.
Output goes to tasks/ by default, --out <dir> to change it. Check what is already in that
directory first: if tasks from a previous run exist, update them rather than writing duplicates.
2. Select the findings
With no arguments, take everything that is critical or high severity, plus every P0/P1 gap,
plus anything named in top_findings or recommended_sequence. Honour explicit selectors when
given: --ids a-bug-01,b-gap-02 · --feature billing · --severity critical · --priority P0 ·
--lens security · --all.
--lens <list> narrows to findings from those lenses — product, security, ux, or all
(the default: every lens in the report). Combines with the other selectors. Note that a task usually
ends up spanning lenses anyway: a security finding and a product finding at the same choke point are
one fix, and step 4 says merge them.
What ships with it
2 files 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.
- 8d ago First seen · 139 lines · 91 tokens per session scan A a8461d88e5f3
feature-tasks is a skill published in the GitHub repository iSerter/claude-feature-recon (6 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,899 once invoked, about $0.0005 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
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.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.