Borrowing it
Nothing to install: this file belongs to sgaabdu4/building-flutter-apps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sgaabdu4/building-flutter-apps/main/AGENTS.mdgit clone --depth 1 https://github.com/sgaabdu4/building-flutter-appsWrote 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/instructions/sgaabdu4/building-flutter-apps/agents-md)<a href="https://agentmods.dev/instructions/sgaabdu4/building-flutter-apps/agents-md"><img src="https://agentmods.dev/badge/instructions/sgaabdu4/building-flutter-apps/agents-md/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/instructions/sgaabdu4/building-flutter-apps/agents-md"><img src="https://agentmods.dev/badge/instructions/sgaabdu4/building-flutter-apps/agents-md.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.00887 | $0.00887 |
| Opus 5.5 | $0.00355 | $0.00355 |
| Sonnet 5.5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade C, and why
building-flutter-apps AGENTS.md scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- No status → from repo root: `curl -fsSL https://raw.githubusercontent.com/sgaabdu4/hard-eng/main/setup.sh | sh` (prepares that branch). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- No status → from repo root: `curl -fsSL https://raw.githubusercontent.com/sgaabdu4/hard-eng/main/setup.sh | sh` (prepares that branch). What it actually says
Agent Rules
.hooks/hard-eng-source.jsonexists → get session's Hard Eng update status before any repo work (read-only too).- SessionStart reports last result + starts/reports a background update; verified → 1 commit on local
hard-eng/updatefrom remote base, current branch untouched. - No status → from repo root:
curl -fsSL https://raw.githubusercontent.com/sgaabdu4/hard-eng/main/setup.sh | sh(prepares that branch). - Prepared branch →
python3 .hooks/hard-eng.py update-pr(opens/reuses PR, auto-merges after checks, no approval; merge denied → rerun--no-merge, give user its printed merge command once checks pass). Exempt from one-PR rules; failing → fix on own branch + worktree first. - Report: updated | no newer verified release | running in background | failed. No updater output = failed (even exit 0); marker/session file alone ≠ success.
- Rerun setup only after failed or no status; never mid-update.
- SessionStart reports last result + starts/reports a background update; verified → 1 commit on local
- Before editing: state the single change, files touched + verification.
- Scope = user request + accepted constraints; preserve unrelated work.
- Project rules =
AGENTS.md(Claude + Codex); move unique legacyCLAUDE.mdrules to the matching one before retiring it; never recreate import wrappers or publish private local instructions. - Before recording tracked content or publishing → apply publication privacy for the audience.
- YAGNI = ultra unless user changes it. Understand the real flow; reuse existing files/code/stdlib/native commands + installed deps before adding code.
- New file/dep/wrapper/abstraction/config/stored state → needs current agreed requirement + why existing code/direct command can't; else omit. Explain in updates; no justification files.
- Comments: none by default; ≤1 terse why-line for a non-obvious constraint names/types/structure/tests can't carry.
checkfails changed source files with longer comment blocks (old ones too). - Fix causes at existing owner. Optional improvements + extra infra only on explicit request; never for robustness/best practice/future needs.
- Tests: each proves a named outcome or catches a specific meaningful failure; reuse first; no implementation mirrors/padding. Name outcomes + failure modes first; tests may follow code, except bug fixes: failing repro test first, expected result from report/contract. Journeys → real E2E where applicable; lower-level tests only for many-case logic + bug repros. Deleting one → state what it protects + replacement proof or why unneeded; E2E overlap alone ≠ enough. testing
- Verification: run applicable gates + prove affected behavior; never hide findings, weaken checks or claim unrun checks passed. Repair every finding in code (unrelated too) as its own commit before continuing; never baseline/tolerate/suppress. Gates stay required even if Hard Eng/updater fails.
- Before done: review diff vs latest request; remove unsupported additions + report remaining expansion. Passing tools/metrics ≠ proof of necessity or test quality.
- Reuse settled approvals; ask only if missing info changes the result or a consequential action lacks approval.
- Output ~80% ASD-STE100: 1 idea/sentence, ≤20 words, active voice, common words, no jargon/idioms; reports = changes, proof, gaps.
- Setup prints
Gap:(missing check/language) → file without asking:python3 .hooks/hard-eng.py gap-issue "<missing check, generic>"; no project names/code/paths/data. - Reproduced fault in Hard Eng's
.hooks/,.agents/skills/he*or setup → tell user, check issues for duplicates, then with approval file a terse one: Problem, Reproduction, installed revision, Suggestion; apply publication privacy. - Follow
.agents/skills/he/SKILL.md; commands:python3 .hooks/hard-eng.py --help.
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.
- yesterday Changed · +6 lines · -6 tokens per session 2734cc09ab2b
- 14d ago Changed · -1 tokens per session 04ea5bd49dc5
- 16d ago Changed · +32 tokens per session 1f2c5a21dbab
- 17d ago First seen · 21 lines · 862 tokens per session scan C 5dbc1d1b07e9
building-flutter-apps AGENTS.md is an instructions file published in the GitHub repository sgaabdu4/building-flutter-apps (25 stars, last pushed 2d ago), licensed MIT. It adds 887 tokens to every session, about $0.0035 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).