Borrowing it
Nothing to install: this file belongs to tatargabor/set-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tatargabor/set-core/main/.claude/skills/set/harvest/SKILL.mdgit clone --depth 1 https://github.com/tatargabor/set-coreWrote 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/tatargabor/set-core/harvest)<a href="https://agentmods.dev/skills/tatargabor/set-core/harvest"><img src="https://agentmods.dev/badge/skills/tatargabor/set-core/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.1 | $0.00000 | $0.00849 |
| Opus 5 | $0.00000 | $0.00425 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
harvest 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- harvest — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harvest framework fixes from consumer project E2E runs.
Input: --project <name> (optional) — scan a single project. Without it, scans all registered consumer projects.
You are a framework maintainer. Your job is to review ISS fixes and template changes from consumer E2E runs and decide which ones should be adopted into set-core.
Quick Start
Run the harvest CLI to see unadopted framework-relevant fixes:
set-harvest --dry-run # preview what's pending
set-harvest --project craftbrew-run-20260320-1445 # scan single project
set-harvest # interactive review all
set-harvest --all # include project-specific fixes too
set-harvest --json # machine-readable output
What It Scans
The harvest tool scans registered consumer projects (from set-project list) for:
- ISS registry — unresolved issues from
.set/issues/registry.jsonwith diagnosed root causes. Framework-relevant issues (orchestrator bugs, gate failures, stall recovery) are surfaced even if no fix commit exists. This catches bugs that were diagnosed but never fixed. - ISS fix commits — commits with
fix:orfix-iss-patterns that were created by the orchestration agent during E2E runs to resolve build/test/e2e gate failures - Template divergences — modifications to
.claude/rules/set-*.mdfiles that were deployed byset-project initbut modified by agents during the run
Issues are classified by keyword analysis of root_cause and error_summary:
- FRAMEWORK — mentions orchestrator, engine, merger, gate, stall, redispatch, worktree
- EXTERNAL — rate limits, API issues
- PROJECT-SPECIFIC — app-level bugs (Suspense, Prisma, Stripe)
Commits are classified by files changed:
- FRAMEWORK — modifies config files (package.json, playwright.config.ts, middleware.ts) → should be reviewed for adoption into planning_rules.txt or templates
- TEMPLATE — modifies
.claude/deployed files → diff against set-core templates - PROJECT-SPECIFIC — only modifies app code → usually skip
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.
- yesterday First seen · 70 lines · 0 tokens per session scan A 6e2bfba07d40
harvest is a skill published in the GitHub repository tatargabor/set-core (35 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 849 tokens. 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-06.
Other skills, from other repositories
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
hatch3r-qa-validation
E2E validation workflow producing a structured pass/fail report with evidence. Use when running QA validation, acceptance testing, verifying releases, or working on QA E2E validation issues.
phoenicurus
Skill "phoenicurus" from markmhendrickson/ateles, covering phoenicurus — qa, identity, agents are the primary users, principals and job.
regression-test-gen
Suggest regression coverage for changed stack behavior.
bug-fix
Systematic workflow for verifying bug fixes to ensure quality and prevent regres...
Test Quality Inspector
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions.