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 tjdrhs90/flutter-flame-harness --skill flame-harness-retrogit clone --depth 1 https://github.com/tjdrhs90/flutter-flame-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/tjdrhs90/flutter-flame-harness/flame-harness-retro)<a href="https://agentmods.dev/skills/tjdrhs90/flutter-flame-harness/flame-harness-retro"><img src="https://agentmods.dev/badge/skills/tjdrhs90/flutter-flame-harness/flame-harness-retro/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/tjdrhs90/flutter-flame-harness/flame-harness-retro"><img src="https://agentmods.dev/badge/skills/tjdrhs90/flutter-flame-harness/flame-harness-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 156 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00032 | $0.03170 |
| Opus 5 | $0.00016 | $0.01585 |
| Sonnet 5 | $0.00006 | $0.00634 |
| Haiku 4.5 | $0.00003 | $0.00317 |
Grade A, and why
flame-harness-retro 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flame-harness-retro
Phase 11 (final) of the flutter-flame-harness pipeline. Scores the completed pipeline against
Anthropic's 9 harness-design principles and game quality criteria, then writes the retrospective
report and sets the pipeline to completed.
All file schemas (config.md, state.md, build-log.md, pipeline-log.md) and the phase
transition table are defined in docs/harness-protocol.md — that document is the single source of
truth (§1 config.md; §2 state.md keys; §3 contract.md layout; §4 handoff layout; §5 feedback
layout; §6 log schemas; §7 retro → complete → status=completed transition). Do not redefine
schemas here.
Boundary: This is the terminal phase. After writing docs/harness/retro.md and updating
state.md, no further skill dispatch occurs. The pipeline ends.
Prerequisites: flame-harness-resume dispatched this skill with next_role: retro; state.md
shows current_phase: retro.
Inputs — Read All Harness Artifacts
Before scoring, load all available evidence:
docs/harness/config.md— extractapp_slug,app_name,max_rounds,strict_mode,skip_research,skip_admob(per protocol §1).docs/harness/state.md— confirmcurrent_phase: retro; readcurrent_round,resume_attempts(per protocol §2).docs/harness/contract.md— review the negotiated Hard Gates and Functional Criteria, and the finalStatus: AGREEDline (per protocol §3).docs/harness/handoff/— read allround-N-gen.mdfiles; note what was built / fixed per round, and any self-assessment failures (per protocol §4).docs/harness/feedback/— read allround-N-qa.mdfiles; note PASS/FAIL verdicts, evidence commands run, and specific failed criteria (per protocol §5).docs/harness/build-log.md— read the full build log table (per protocol §6).docs/harness/pipeline-log.md— read the full pipeline event log (per protocol §6).- Git log: run
git log --onelineto count commits and identify rework patterns.
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 · 324 lines · 32 tokens per session scan A 5ea1d87a4d6c
flame-harness-retro is a skill published in the GitHub repository tjdrhs90/flutter-flame-harness (60 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 3,170 once invoked, about $0.0002 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
achievements
Steam-style achievement system with XP, levels, streaks, and skill trees. Gamifies the development workflow. 25 achievements across 5 categories.
variable-rewards
Generates a variable reward system with randomized rewards, daily bonuses, mystery box mechanics, and ethical engagement caps. Use when user wants daily spins, mystery boxes, random rewards, or gamification reward systems.
game-development
Game development with Unity, Unreal Engine, and Godot. Use when building games, implementing game mechanics, physics, AI, or working with game engines.
ar-vr-xr
AR/VR/XR development with Unity XR, WebXR, ARKit, ARCore, Meta Quest SDK, and spatial computing. Use when building augmented reality, virtual reality, mixed reality applications, or spatial experiences.
fabrik-validate
Use when operating as the Fabrik Validate stage agent. This skill guides final validation of an implementation, verifying requirements are met, tests pass, and the PR is ready to merge.
architecture-foundations
Interviews the technical architect about the foundations a project is built on — the immovable constraints, the shared domain model and which feature owns each field, the interface contracts between features, and the authority model governing who can do what. Runs early, before experience design, and is re-run as…