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 fiveonecode/agent-skills --skill lifecycle-and-side-effects-correctnessgit clone --depth 1 https://github.com/fiveonecode/agent-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/fiveonecode/agent-skills/lifecycle-and-side-effects-correctness)<a href="https://agentmods.dev/skills/fiveonecode/agent-skills/lifecycle-and-side-effects-correctness"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/lifecycle-and-side-effects-correctness/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/fiveonecode/agent-skills/lifecycle-and-side-effects-correctness"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/lifecycle-and-side-effects-correctness.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.00088 | $0.00872 |
| Opus 5.5 | $0.00035 | $0.00349 |
| Sonnet 5.5 | $0.00018 | $0.00174 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
lifecycle-and-side-effects-correctness 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 1mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle And Side Effects Correctness
Overview
Use this skill to prevent duplicate, stale, missing, or misattributed side effects across lifecycle transitions. Treat analytics, purchases, network retries, persistence, and callbacks as contract-bearing effects, not incidental code inside a view or async closure.
Workflow
1. Identify the owner
- Name the durable owner for each effect: service, coordinator, store, view model, view task, or external SDK.
- Keep one-shot effects out of view identity when remounts,
.id(...), previews, or sheet recreation can run the code again. - Separate view-local state from session, purchase, analytics, or persisted state.
2. Map lifecycle transitions
List the transitions that can start, repeat, cancel, or complete work:
- appear, disappear, dismiss, remount, reload, retry, background, foreground;
- task start, cancellation, timeout, success, failure, fallback;
- purchase start, product/offering reload, checkout, restore, completion;
- analytics impression, dismiss, branch, conversion, error, and retry.
For each transition, write the expected state and allowed side effects.
3. Enforce side-effect invariants
- No duplicate side effects from view remount,
.taskrestart,.onAppear,.id(...), or sheet recreation. - No stale completion side effects after cancellation, dismissal, navigation away, or superseded input.
- No false dismiss/present, impression, purchase, or retry analytics caused by view identity churn.
- In-flight purchase or mutation actions are idempotent, disabled, or otherwise guarded.
- Retry paths emit required lifecycle events exactly as specified and preserve session attribution.
- Failure paths either emit the required failure effect or explicitly suppress it under a documented rule.
- Persisted state, analytics properties, and user-visible copy derive from the same canonical source when they describe the same decision.
4. Check identity and attribution
- Define the stable session, impression, request, purchase, or operation ID before work starts.
- Preserve attribution through retries, slow loads, fallback, and personalized copy refresh.
- Do not derive experiment, package, offering, campaign, or branch attribution from display text when a canonical ID exists.
- Normalize stale IDs only at the boundary that owns the crosswalk; do not let tests erase identity bugs through broad normalization.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 78 lines · 88 tokens per session scan A 5f8dd0b3712e
lifecycle-and-side-effects-correctness is a skill published in the GitHub repository fiveonecode/agent-skills (19 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 872 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
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…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp: publish the Windows head first, then point packaging at the resolved resizetizer manifest. Use for a MAUI MSIX or signed unpackaged build, MAUI packaging in CI, or 'manifest contains unresolved placeholders' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…