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 chrono-meta/forge-harness --skill field-harvestgit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/field-harvest)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/field-harvest"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/field-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/chrono-meta/forge-harness/field-harvest"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/field-harvest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00095 | $0.03722 |
| Opus 5 | $0.00048 | $0.01861 |
| Sonnet 5 | $0.00019 | $0.00744 |
| Haiku 4.5 | $0.00010 | $0.00372 |
Grade A, and why
field-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 11d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
field-harvest — Field Pattern Harvest → FH Backport + Session Logger
Dual-mode skill:
- Mode A (Pattern Harvest): Scans recent commits in field projects to detect patterns worth backporting to FH. One-click flow from detection to PR creation.
- Mode B (Session Log): Records session work from field projects to the knowledge hub when a session ends. Auto-generates a session markdown file with commits, learnings, and next steps.
Mode Selection (Step 0-A)
Determine which mode to run based on user context:
| Condition | Mode | Priority |
|---|---|---|
| User message contains: "session log", "log today's work", "sync to hub", "sync session" | Mode B (Session Log) | 1 (highest) |
| Session-end auto-trigger fires (see below) and field commits exist today | Mode B (Session Log) — auto-proposed | 2 |
| Both Mode A and B applicable | Run Mode B first, then ask "Also run Mode A pattern harvest?" | 3 |
| Default or path specified | Mode A (Pattern Harvest) | 4 |
Session-End Auto-Trigger (item1 — Mode B)
Mode B should not wait for an explicit "session log" phrase when a session is plainly ending with un-logged field work. Auto-propose Mode B (one line, never auto-run) when all hold:
- A session-close signal is detected — the CLAUDE.md Session Wrap-up chain has begun, or the user says a closing phrase ("wrap up", "done", "good work", "end session", "that's it for today").
- The current cwd is a mapped field project (not the FH hub itself — hub close is owned by harvest-loop / the Session Wrap-up chain).
git log --since="today"in that field project returns 1+ commits by the session author that are not yet logged to the hub (cross-check via the detection-skip ledger, item2 below).
Proposal format (one line, then wait):
"Session is wrapping up and {project} has N un-logged commits today. Log them to the hub with Mode B? [y/n]"
Collision guard (harvest-loop boundary): "wrap up" / "end session" in the FH hub cwd stay owned by the CLAUDE.md Session Wrap-up chain (which calls harvest-loop). This auto-trigger is field-cwd only and is a proposal, never an interception — if harvest-loop is already running for this session, do not also propose Mode B (harvest-loop calls field-harvest internally as Step H1). One proposal per session.
What ships with it
1 file 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.
- 11d ago First seen · 268 lines · 95 tokens per session scan A e632add2f9b9
field-harvest is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 3,722 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-30.
Other skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.