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/danielmiessler/lifeos/isanpx skills add danielmiessler/LifeOS --skill isagit clone --depth 1 https://github.com/danielmiessler/LifeOSWrote 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/danielmiessler/lifeos/isa)<a href="https://agentmods.dev/skills/danielmiessler/lifeos/isa"><img src="https://agentmods.dev/badge/skills/danielmiessler/lifeos/isa.svg" alt="Measured on agentmods" 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 | $0.00115 | $0.06657 |
| Opus 5 | $0.00057 | $0.03328 |
| Sonnet 5 | $0.00023 | $0.01331 |
| Haiku 4.5 | $0.00012 | $0.00666 |
Grade A, and why
ISA scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://localhost:31337/notify \ How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)
You MUST send this notification BEFORE doing anything else when this skill is invoked.
-
Send voice notification:
curl -s -X POST http://localhost:31337/notify \ -H "Content-Type: application/json" \ -d '{"message": "Running the WORKFLOWNAME workflow in the ISA skill"}' \ > /dev/null 2>&1 & -
Output text notification:
Running the **WorkflowName** workflow in the **ISA** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
ISA — Ideal State Artifact
What It Does
The ISA is the single document that articulates "done" for any thing whose ideal state we are pursuing — a project, an application, a library, infrastructure, a work session, an art piece, a strategic decision. It serves five identities at once: ideal state articulation, test harness, build verification, done condition, system of record. This skill owns the canonical template, the workflows that generate and refine ISAs, and the example library.
Every ISA shares one meta-ideal-state above its specific one: euphoric surprise in the human using the system. The specific ideal state varies with the work; the universal one never does. ## Vision is where that general target takes specific shape — what euphoric surprise looks like for this particular work — so every ISA hill-climbs toward two summits at once.
The Problem
Most work starts without a written, testable definition of what finished looks like, so "done" drifts — the goal in your head at the start isn't the goal you settle for at the end, and there's no record of which one was right. Criteria stay vague enough that anything passes, decisions and dead ends get forgotten and re-litigated, and when work spans multiple sessions or multiple agents there's no shared source of truth for what's been verified. The ISA fixes "done" as a hard-to-vary explanation with atomic, probe-able criteria, a stable-ID structure that survives edits, and an audit trail of what was conjectured, refuted, and learned.
What ships with it
19 files 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.
- Examples/canonical-isa.md 18 KB
- Examples/e1-minimal.md 1.6 KB
- Examples/e2-backup-verify.md 5.4 KB
- Examples/e2-rotate-credential.md 5.4 KB
- Examples/e3-essay.md 13 KB
- Examples/e3-help-redesign.md 13 KB
- Examples/e3-project.md 4.1 KB
- Examples/e4-api-migration.md 25 KB
- Examples/e4-brand-identity.md 24 KB
- Examples/e5-album.md 21 KB
- Examples/e5-desktop-app.md 21 KB
- Examples/e5-enterprise.md 37 KB
- Workflows/Append.md 6.8 KB
- Workflows/CheckCompleteness.md 12 KB
- Workflows/Grill.md 5.5 KB
- Workflows/Interview.md 4.7 KB
- Workflows/Reconcile.md 6.1 KB
- Workflows/Scaffold.md 16 KB
- Workflows/Seed.md 6.8 KB
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.
- 4d ago First seen · 245 lines · 115 tokens per session scan A 3e5745ccdb63
ISA is a skill published in the GitHub repository danielmiessler/LifeOS (18,865 stars, last pushed 19d ago), licensed MIT. It adds 115 tokens to every session and 6,657 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
echo-plugins
Build, validate, package, and stage optional Echo plugins using the Echo Plugin API v1 security and lifecycle contracts.
browser-spa-framework
Architecture/conventions for the Echo browser SPA: Go stdlib server :3740, Vite-built TS+JS SPA (embedded web/dist), JSON envelope, WebSocket hub, chat tool loop, shared appdata echo.json, internal/tools registry, tool-generated media transport (Phase 0/1), and the file-browser image/video/audio preview surface…
global-notifications
How Echo surfaces cross-surface/cross-tab alerts to the user: global WebSocket broadcasts (chatcompleted, planquestionsawaiting) mirrored by frontend notification modules that play sounds, show OS/browser Notifications, and deep-link on click.
update-change-log
To synchronize CHANGELOG.md with changes made last week (mon - sun).
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…