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 agentmods add skills/strvcom/flutter-template/secrets-bootstrapnpx skills add strvcom/flutter-template --skill secrets-bootstrapgit clone --depth 1 https://github.com/strvcom/flutter-templateWhat 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 | $0.00043 | $0.00443 |
| Opus 5 | $0.00022 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
secrets-bootstrap 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.
What it actually says
Flutter Template Secrets Bootstrap
Use this skill when a task requires secret handling in this repository.
Read First
AGENTS.mdREADME.mdextras/secrets/tools/android/extras/keystores/README.mdmakefile
Safety Rule
Do not touch secrets unless the task clearly requires it.
That includes:
.env.env-development.env-staging.env-production- keystore files
- encrypted secret files in
extras/secrets/ - generated iOS config files
Workflow
- Confirm why secret access is needed.
- Inspect the existing secret-loading scripts instead of improvising commands.
- Prefer existing make targets and scripts:
make secretsDecryptmake secretsEncryptmake secretsClean
- Keep encrypted files and generated decrypted files conceptually separate.
- Avoid logging secret values in output, comments, or diffs.
- If a task only needs to know whether a value exists, verify presence without printing contents.
Repo Notes
- Secret tooling lives under
extras/secrets/tools/. - README documents the expected
ageandsopsflow. - Android keystore guidance has its own README.
- Environment files are referenced by
pubspec.yamland loaded by flavor inlib/app/setup/setup_app.dart.
When To Stop And Ask
- the task needs a missing secret
- the task would rotate or overwrite encrypted files
- the task would expose secret contents in logs or committed files
- the task needs signing or distribution credentials that are not already available
Completion Criteria
- used existing scripts or make targets where possible
- avoided exposing sensitive values
- explained clearly what was loaded, generated, or still missing
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 First seen · 58 lines · 43 tokens per session scan A 1208f36b8393
secrets-bootstrap is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 443 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
speckit-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
add-sample
Create a SamplesApp sample page with correct theming and attributes. Use when adding UI samples for controls.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…