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-status-summarygit 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-status-summary)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/frontier-status-summary"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/frontier-status-summary/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-status-summary"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/frontier-status-summary.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.00039 | $0.01929 |
| Opus 5.5 | $0.00016 | $0.00772 |
| Sonnet 5.5 | $0.00008 | $0.00386 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
frontier-status-summary 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED (2026-05-18): ~80% dependency on personal assets; does not meet FH general-purpose skill criteria. The core value of audience-based asset cross-referencing is absorbed into install-wizard Step 0-A (FH suitability pre-flight).
frontier-status-summary — Frontier Status + External Distribution Asset Cross-Reference
A skill for cross-referencing externally distributed assets by audience type, created after reaching Phase I completion and Phase II entry signals. No asset transformation — invocation tools only (consistent with simplification principle — 0 new assets created).
Trigger Utterances
Utterance patterns:
- Status summary request: "show frontier status", "where are we at", "where are we now", "what Phase are we at"
- External distribution material alignment: "align external distribution materials", "materials for {audience}", "what do I show to {audience}"
- Identity cross-reference: "meta harness identity", "differentiating message", "unique value"
- Audience-based invocation: "for engineers", "for decision-makers", "for non-technical audience", "external presentation"
Exceptions (this skill does not apply):
- Request to directly edit asset content → edit the asset directly (no cross-ref needed)
- Request to write new asset → do not call this skill · only cross-ref 4 assets for audience classification then determine new audience/volume/axis
Asset Matrix
| # | Asset | Audience | Volume | Channel | Status | Axis |
|---|---|---|---|---|---|---|
| 1 | briefings/harness_engineering_intro.md |
Engineers (org-wide) | ~3 pages | Wiki / doc sharing | published | 2·3 |
| 2 | briefings/expected_roi_meta_harness.md |
Decision-makers + engineers | Table-heavy | (TBD — follow-up to #1) | draft | 6 |
| 3 | briefings/harness_intro_outsider_guide.md |
Non-technical / external | 5-minute read | Slack canvas → wiki | first distribution decided | 3 |
| 4 | briefings/frontier_arrival_report.md |
All 3 audiences combined | ~3 pages | (review before external send) | draft | 1·2·3·6 |
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 · 140 lines · 39 tokens per session scan A 33c238f11879
frontier-status-summary is a skill published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,929 once invoked, about $0.0002 per session on Opus 5.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-09-04.
Other skills, from other repositories
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, UI mockups, product shots, or transparent-background cutouts. Use when the result should be an image asset rather than repo-native SVG, HTML/CSS, or canvas.
a2ui
Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a callout, a Mermaid diagram, a weather card, a live clock or countdown, a dashboard of gauges for a quota, a budget or a…
oma-design
Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
visual-acceptance
A visual final-review method for user-interface changes. It checks the rendered result with repeatable screenshots, pixel values, computed styles, and CSS layering checks across themes.
commonly-design
Use this skill for ANY visual / UI / design work on Commonly — picking colors, choosing fonts, styling new v2 components, building HTML mocks, designing marketing pages, or auditing whether a change matches the brand. Triggers on tasks involving v2.css tokens, accent / blue / focus ring / SF font, brand mark / logo…
ui-resilient-accessibility
Build and review UI components for robust accessibility and runtime resilience, including semantic structure, keyboard support, loading and error states, retry flows, and predictable async behavior.