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 frontier-digestgit 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/frontier-digest)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/frontier-digest"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/frontier-digest/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/frontier-digest"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/frontier-digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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.
- medium Rogue Agent · line 109 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00071 | $0.03567 |
| Opus 5 | $0.00036 | $0.01784 |
| Sonnet 5 | $0.00014 | $0.00713 |
| Haiku 4.5 | $0.00007 | $0.00357 |
Grade A, and why
frontier-digest scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **Detail**: See `SKILL_detail.md §Collection-Bash` — curl commands per source with parsing notes — read when executing Step 1. How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frontier-digest — FH Frontier Insight Collection & Synthesis
Automatically collects the latest AI/agent/harness engineering trends from HackerNews and arxiv, then compresses and synthesizes them into insights directly relevant to forge-harness skills and structure.
Triggers
/frontier-digest # immediate execution
/frontier-digest --save # save result to file
"what's on the frontier"
"this week's AI trends"
"harness trends"
"latest agent developments"
"any ideas for improving the harness?"
Step 0. API Environment Detection
This is the trend-scan specialization (rung 3) of the Deep-Research Capability Ladder
(../../../../knowledge/shared/harness-core/deep_research_capability_ladder.md). The ladder owns
the cross-rung routing (when a task is trend-scan at all vs general research); the Priority:
block below is frontier-digest's own internal engine resolution for the HN/arxiv case (API-key
vs WebSearch) — a narrower detection, not a re-definition of the cross-rung ladder.
Priority:
0. /deep-research built-in available (check live session skill list)
→ use it as the collection+verification engine (staged source gathering,
cross-checking, cited synthesis) — Tier-0 route, no API key needed
1. ANTHROPIC_API_KEY environment variable → Claude Sonnet
2. Neither → WebSearch mode (raw data only, no synthesis)
Report detection result in one line. Example: 🔑 Using Claude Sonnet / 🔑 Engine: /deep-research (built-in)
On first run without an API key, output the environment setup guide (format in §Output-Formats).
Step 0.5. Operator Intake (speculative-interview arm — walled channels)
On cadence-triggered runs (7d), ask the operator one line before collecting:
"이번 주에 본 벽 뒤 소스(YouTube·LinkedIn·X 등 기계가 못 닿는 링크/요약)가 있으면 던져 주세요 — triage해서 기록합니다. 없으면 그냥 진행할게요."
- Operator may skip — zero pressure; the autonomous arms (Step 1) run regardless.
- Why: walled channels return 403 to machine fetch — the operator is the only wide-net sensor for them. This arm turns ad-hoc link-throwing into a scheduled intake (manual-validated n=2).
- Received sources route to the sister-asset/triage flow with its lightweight path: C-tier (territory already covered) = one-paragraph entry only; full cross-audit reserved for A/B-tier. Partial wall-bypass is allowed first: try WebSearch + secondary sources before declaring unfetchable.
- Video sources (local/laptop only — cloud VMs typically 403 on video hosts): probe by capability, not engine name via the Sidecar Engine Resolution Protocol. Tier 1 = natively multimodal CLI ingesting the URL directly (⚠️ direct
geminiCLI EOL 2026-06-18 — probeagyor the Gemini API after); never route video to a coding-agent CLI without native video access (it burns tokens and recovers only metadata). Tier 3 =yt-dlptranscript fallback, conditional — probe the environment first, never assume it works. Unresolvable → operator summary remains the path.
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.
- 4d ago Changed 0f6c9ea80626
- 9d ago First seen · 232 lines · 71 tokens per session scan A 6dac1008b1ac
frontier-digest is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 3,567 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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-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-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.