flame-harness-status

flame-harness-status is a skill for Claude Code from tjdrhs90/flutter-flame-harness. It costs 24 tokens per session (868 once invoked), scanned A, original, MIT.

A read-only status reporter for the Flutter Flame Harness, a workflow that builds Flutter games. It summarizes the current phase, round, scores, and any pause information from the workflow files.

In plain words
What is it for?
It checks whether a pipeline is active and reports its current progress from the state, build, and pipeline log files.
Why use it?
It lets you inspect a run without changing its state or accidentally advancing the workflow.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the flutter-flame-harness plugin — 14 skills shipped together

Good fit It checks whether a pipeline is active and reports its current progress from the state, build, and pipeline log files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tjdrhs90/flutter-flame-harness/flame-harness-status
Install

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.

Any agent
npx skills add tjdrhs90/flutter-flame-harness --skill flame-harness-status
Clone the repo
git clone --depth 1 https://github.com/tjdrhs90/flutter-flame-harness

Made for: Claude Code.

Or install flutter-flame-harness, the plugin that ships this one along with the rest of its 14 skills.

Wrote 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.

agentmods badge for flame-harness-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/tjdrhs90/flutter-flame-harness/flame-harness-status/github.svg)](https://agentmods.dev/skills/tjdrhs90/flutter-flame-harness/flame-harness-status)
Your own site
<a href="https://agentmods.dev/skills/tjdrhs90/flutter-flame-harness/flame-harness-status"><img src="https://agentmods.dev/badge/skills/tjdrhs90/flutter-flame-harness/flame-harness-status/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.

agentmods 80×15 button for flame-harness-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/tjdrhs90/flutter-flame-harness/flame-harness-status"><img src="https://agentmods.dev/badge/skills/tjdrhs90/flutter-flame-harness/flame-harness-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 868 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00868
Opus 5 $0.00012 $0.00434
Sonnet 5 $0.00005 $0.00174
Haiku 4.5 $0.00002 $0.00087

Measured 10d ago against content hash 5a17d0c3940a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

flame-harness-status 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 10d 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.

skills/flame-harness-status/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

flame-harness-status

Read-only status reporter for the flutter-flame-harness pipeline. Reads state.md, build-log.md, and pipeline-log.md and prints a summary of the current pipeline state.

All file schemas (state.md, build-log.md, pipeline-log.md) are defined in docs/harness-protocol.md — refer to that document as the single source of truth. Do not redefine schemas here.

This skill is strictly read-only. It must never modify state.md or any other harness file.


Input

Locate docs/harness/state.md relative to the current project root (the directory that contains docs/harness/). If state.md does not exist, print:

flame-harness-status: no active pipeline found (docs/harness/state.md missing).
Run /flame-harness <idea> to start a new pipeline.

Then exit without error.


Procedure

1. Read state.md

Read docs/harness/state.md and extract the following fields per the schema in docs/harness-protocol.md §2:

  • statusrunning | paused | completed
  • current_phase — name of the currently executing phase
  • current_round — integer round counter
  • next_role — skill role that runs next
  • pause_reason"" | rate_limit | manual_action | error
  • updated_at — ISO-8601 timestamp of last write
  • resume_attempts — integer

2. Read build-log.md (if present)

Read docs/harness/build-log.md per the schema in docs/harness-protocol.md §6. Extract the latest row to obtain the most recent QA score (PASS | FAIL | PARTIAL) and the round number it corresponds to. If the file is absent or has no data rows, set latest_score to .

3. Read pipeline-log.md (if present)

Read docs/harness/pipeline-log.md per the schema in docs/harness-protocol.md §6. Extract the last 3 rows to give a recent event summary. If the file is absent or empty, skip.

4. Print status report

Print the following formatted report (adapt spacing for readability):

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 flame-harness pipeline status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Status        : <status>
  Current phase : <current_phase>
  Round         : <current_round>
  Next role     : <next_role>
  Latest QA     : <latest_score>
  Last updated  : <updated_at>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Read the full file on GitHub · 111 lines

Changes

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.

  1. 10d ago First seen · 111 lines · 24 tokens per session scan A 5a17d0c3940a

Subscribe to this mod's changes

flame-harness-status is a skill published in the GitHub repository tjdrhs90/flutter-flame-harness (60 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 868 once invoked, about $0.0001 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.