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 ariaramin/flutter-skills --skill hydrated-blocgit clone --depth 1 https://github.com/ariaramin/flutter-skillsWrote 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/ariaramin/flutter-skills/hydrated-bloc)<a href="https://agentmods.dev/skills/ariaramin/flutter-skills/hydrated-bloc"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/hydrated-bloc/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/ariaramin/flutter-skills/hydrated-bloc"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/hydrated-bloc.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.00068 | $0.06210 |
| Opus 5.5 | $0.00027 | $0.02484 |
| Sonnet 5.5 | $0.00014 | $0.01242 |
| Haiku 4.5 | $0.00007 | $0.00621 |
Grade A, and why
hydrated-bloc 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 12d 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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hydrated_bloc — Production Flutter Skill
Purpose
Teach an AI coding agent how to use hydrated_bloc correctly in production Flutter apps: when to hydrate, how to initialize storage, how to serialize safely, how keys/identity work, how errors and schema changes behave, and how to test without leaking state—based on official package docs, API, source, tests, examples, and changelog (stable 11.0.0 as of research).
Agent behavior rules (mandatory)
Before changing hydration-related code:
- Inspect
pubspec.yaml/ lockfile for the installedhydrated_bloc(andbloc) version. Do not use APIs from a different major. - Inspect existing Bloc/Cubit architecture; reuse project patterns when correct.
- Do not convert a normal Bloc/Cubit to hydrated without a real post-restart persistence need.
- Identify exactly which fields must survive process death; persist only those.
- Do not persist secrets/tokens through default storage without an explicit security design.
- Before changing serialized shape, class names,
storagePrefix, orid, consider already-installed app versions and existing persisted keys. - Prefer reconstructing derived values over persisting them.
- Keep
toJson/fromJsondeterministic and defensive. - Avoid introducing a second source of truth (e.g. hydrating the same data the backend already owns).
- Add/update tests whenever hydration, keys, schema, or clear/logout behavior changes.
- Validate platform assumptions (especially web vs IO directory, and temporary vs durable paths).
- Do not invent migration APIs, sync guarantees, or encryption properties the package does not provide.
When to Use This Skill
- Persisting small durable UI/workflow state across app restarts (theme, filters, onboarding step, draft flags).
- Implementing or reviewing
HydratedCubit/HydratedBloc/HydratedMixin. - Fixing lost state after rename, minify/obfuscate, or web rebuild (
storagePrefix). - Logout / account switch / cache clear flows.
- Hydration errors, corrupted JSON, schema upgrades.
- Unit/widget tests that touch hydrated types.
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.
- 12d ago First seen · 553 lines · 68 tokens per session scan A ba9802961e31
hydrated-bloc is a skill published in the GitHub repository ariaramin/flutter-skills (2 stars, last pushed 12d ago), licensed MIT. It adds 68 tokens to every session and 6,210 once invoked, about $0.0003 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-25.
Other skills, from other repositories
beta-testing
Beta testing strategy for iOS/macOS apps. Covers TestFlight program setup, beta tester recruitment, feedback collection methodology, user interviews, signal-vs-noise interpretation, and go/no-go launch readiness decisions. Use when planning a beta, setting up TestFlight, collecting user feedback, or deciding if ready…
speq-planning
Plan-authoring workflow — spec delta authoring, test mapping, plan.md/decision-log.md generation, expert-task tagging, headless escalation, and revision mode. Triggered by planner-agent.
speq-implement-pr
Headless follow-up to /speq-plan-pr. Continues a plan on its feat/plan-name branch and runs it end-to-end: implements via /speq-implement, bumps the version, commits and pushes, runs the real test suites, records only if green, then opens/updates the PR and marks it ready. Resumes from the PR Lifecycle checkpoint in…
speq-implement
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
speq-code-guardrails
TDD cycle and code quality guardrails — failing-test-first, evidence, dependency, error-handling, and test-quality rules. Triggered by implementer-agent, implementer-expert-agent, and code-reviewer before any implementation or review work.
test-xcode
Build and test iOS apps on simulator using XcodeBuildMCP.