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 agentmods add skills/rakovi4/continue-framework/harvestnpx skills add rakovi4/continue-framework --skill harvestgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/harvest)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/harvest"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/harvest.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 | $0.00071 | $0.01545 |
| Opus 5 | $0.00036 | $0.00772 |
| Sonnet 5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade B, and why
harvest 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
(`grep -F 'Tier: 2'` per file, per `.claude/templates/spec/tier-ladder.md`) whose How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/harvest — Tier 1 → Tier 2 Boundary Batch
Dispatched by /continue from the - [ ] harvest checkbox that sits between the
last Tier 1 section and the first Tier 2 one in a tier-major progress.md
(.claude/templates/workflow/progress-format.md). Untiered stories have no such
checkbox and never reach this skill.
Why a skill, not an inline /continue phase. Harvest fans out concurrent
red-agents, then stops the backend and boots a second build of the application to
baseline the result — far past what an inline gate like adapters-discovery does.
Run it inline in the main agent (like green-acceptance and the story spec
item): it dispatches its own sub-agents, which must not nest inside a wrapper agent.
What it buys. Many Tier 2 scenarios already pass the moment Tier 1 is green.
Discovering that one red-acceptance work unit at a time pays a full unit each. One
batch step runs them all at once.
Scope: acceptance level only. Only black-box-over-HTTP acceptance tests can be
pointed at a differently-built application; usecase and adapter tests compile against
production classes and cannot be baselined (CLAUDE.md). Harvest touches
acceptance/ test code and progress.md — never production code.
The batch
- Read
tests/*.mdand collect every scenario carrying an inlineTier: 2marker (grep -F 'Tier: 2'per file, per.claude/templates/spec/tier-ladder.md) whose acceptance step is not yet done. These are the harvest set. - Fan out one
red-agentper scenario, concurrently (dispatch them in a single message — layeracceptance, given the scenario name and story folder). Each runs its normal red-acceptance workflow — no harvest-special writer mode. red-agentself-partitions per its own rules:- Green as-is (the test passes the moment it is written): red-agent marks the
scenario's
red-acceptance[x]and every other step for that scenario[S]— its standard "test already passes" branch. The scenario is resolved. - Red: red-agent produces the normal disabled
red-acceptancedeliverable and the scenario continues its ordinary Tier 2 cycle later. Nothing is deleted — the red test is the start of that cycle.
- Green as-is (the test passes the moment it is written): red-agent marks the
scenario's
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.
- 4d ago First seen · 109 lines · 71 tokens per session scan B b4f29e195a7a
harvest is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 1,545 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…