Borrowing it
Nothing to install: this file belongs to tatargabor/set-copilot. 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-copilot/master/.claude/skills/set/harvest/SKILL.mdgit clone --depth 1 https://github.com/tatargabor/set-copilotWrote 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-copilot/harvest)<a href="https://agentmods.dev/skills/tatargabor/set-copilot/harvest"><img src="https://agentmods.dev/badge/skills/tatargabor/set-copilot/harvest/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/tatargabor/set-copilot/harvest"><img src="https://agentmods.dev/badge/skills/tatargabor/set-copilot/harvest.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.00000 | $0.00849 |
| Opus 5.5 | $0.00000 | $0.00340 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to harvest — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 70 lines · 0 tokens per session scan A 6e2bfba07d40
harvest is a skill published in the GitHub repository tatargabor/set-copilot (3 stars, last pushed 20d ago), 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. It is 100% identical to harvest, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
jira-validate-production
Check that the fix a Jira issue carries is live on the PRODUCTION site and behaves as the issue asked, then close the card, or open a follow-up issue for what failed. Insert into the prompt of a run started on a batch of merged issues, or of a Jira post-deploy column rule.
acceptance-criteria-gwt
Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases.
pm-uat-review
Use when a task is in pmuat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to humanuat or needrevision.
testrail
Sincronizar testes com TestRail. Use quando o usuário mencionar "testrail", "gestão de testes", "casos de teste", "execução de testes", "sincronizar casos de teste", "enviar resultados para testrail" ou "importar do testrail".
retest-after-revision
Use when the task came back to QA after needrevision - what to re-run, what may carry over, and how to keep old passes from approving new code.
evidence-publish
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.