Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sgaabdu4/building-flutter-appsnpx agentmods add skills/sgaabdu4/building-flutter-apps/he-buildWrote 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/sgaabdu4/building-flutter-apps/he-build)<a href="https://agentmods.dev/skills/sgaabdu4/building-flutter-apps/he-build"><img src="https://agentmods.dev/badge/skills/sgaabdu4/building-flutter-apps/he-build/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/sgaabdu4/building-flutter-apps/he-build"><img src="https://agentmods.dev/badge/skills/sgaabdu4/building-flutter-apps/he-build.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.00051 | $0.01185 |
| Opus 5.5 | $0.00020 | $0.00474 |
| Sonnet 5.5 | $0.00010 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
he-build 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 2d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hard Eng Build
- Baseline (checks before your edits) fails → repair only that, as its own change + PR; no feature edits until it merges (repair route).
- Input = Ready + authorized plan from HE Plan; check its evidence (passing baseline, UX, blockers), not Status alone. Other missing, pending or contradictory readiness → that owner before production edits. Material scope change → same owner; preserve accepted decisions + completed work. Participation and project context → HE workflow.
- Output = locally implemented + verified behavior, Complete plan (none for a change
checkratesSize: small) and explicit Ready for ship handoff. Build adds no authority to commit, push, publish, merge or deploy; delivery is a separate stage.
Implement + verify
flowchart TD
B[Next complete behavior] --> T[Implement + focused checks]
T --> R[Review actual diff + affected proof]
R --> V{Pass?}
V -->|No| F[Diagnose + fix owner]
F --> T
V -->|Yes| N{Remaining build work?}
N -->|Yes| B
N -->|No| I[Integrated proof + Complete gate]
I -->|Fail| F
I -->|Pass| H[Ready for ship]
click T "../he/references/testing.md"
click R "../code-review/SKILL.md"
click F "../research/references/troubleshooting.md"
click I "../he/references/gates.md#plan-checks"
- Behavior = required connected callers, persistence, API and interface work; a skeleton or file checklist is not an accepted outcome. Keep changes at existing owners; apply relevant stack/design/security guidance only for the changed boundary.
- Proof = test quality + actual-diff review; outside service → fake at its boundary from real responses, tests never call the real one; required runtime journeys, visual evidence and applicable accessibility states → E2E. PR evidence selection → HE Ship. Reuse these owners for regression, defect reopening and review findings; no duplicate checker or mandatory test/agent count.
- Direct test/build/check runs = limit ≈3× normal, ≥15 min (macOS:
perl -e 'alarm shift; exec @ARGV' <s> <cmd>); hit → read log, kill leftover children, rerun. - Progress = same plan + remaining work. Retain the actual starting-baseline outcome + evidence; record later build results in Verification. Keep Status Ready and Verification Pending during an unblocked feature build; baseline repair follows HE Plan's Draft route above. A material decision or unavailable prerequisite → Draft + exact blocker/resume condition; preserve completed steps and continue independent authorized work. Never replace missing proof with a pass or N/A.
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.
- 2d ago Changed · +2 lines e53c807ee0f3
- 18d ago First seen · 46 lines · 51 tokens per session scan A 64b73f1de0e0
he-build is a skill published in the GitHub repository sgaabdu4/building-flutter-apps (25 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,185 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-29.
Other skills, from other repositories
fl-testing
Writes unit and widget tests for blocs, repositories, and screens using bloctest + mocktail.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).