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 JanoshMoshiri/MarkdownLLM --skill life-manager-specificationgit clone --depth 1 https://github.com/JanoshMoshiri/MarkdownLLMWrote 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/janoshmoshiri/markdownllm/life-manager-specification)<a href="https://agentmods.dev/skills/janoshmoshiri/markdownllm/life-manager-specification"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/life-manager-specification/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/janoshmoshiri/markdownllm/life-manager-specification"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/life-manager-specification.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.00019 | $0.01379 |
| Opus 5 | $0.00010 | $0.00690 |
| Sonnet 5 | $0.00004 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
Life Manager Specification 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Life Manager Specification
Philosophy
This is not an app. It is a paradigm shift in how life management works.
Traditional apps separate concerns: input happens through UI, processing happens in code, output is notifications and data views. You think about wiring these together, building conditional logic, managing state in databases.
This system inverts that model entirely.
Processing: A capable LLM agent becomes your reasoning engine. The agent understands context, makes sense of complexity, handles ambiguity, reasons about priorities and dependencies. This is not rule-based logic—it's semantic understanding.
Interface: Your phone is pure interface and notification hub. You talk to your agent. You receive reminders and calendar updates. The phone is how you interact and how you get notified.
Storage: Git repository with markdown files is your persistent state. Not because it's clever, but because it's durable, versioned, readable by human and agent alike, and completely vendor-agnostic. Your life data lives in markdown. The LLM reads it, reasons about it, updates it.
The Paradigm Shift
You stop thinking about "how do I build this app" and start thinking about "how do I structure my data so the agent can understand and reason about it."
The complexity doesn't disappear—it just moves. Instead of writing conditional logic and integration code, you're defining how the agent should think about your life. Instead of predefined schemas, you let structure emerge based on what your life actually needs.
How It Works
- Your life exists as a collection of "things" in a git repository
- Each thing is a markdown file with YAML metadata and narrative body
- When you need help, you talk to the agent (via your phone, via any interface)
- The agent reads the relevant things, understands the structure and context
- The agent reasons about what you're asking, what matters, what's next
- The agent updates your thing files, creates reminders, updates your calendar
- Your phone notifies you of changes and reminders
- You talk to the agent again with new information or requests
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.
- 9d ago First seen · 117 lines · 19 tokens per session scan A db6b8e6a0822
Life Manager Specification is a skill published in the GitHub repository JanoshMoshiri/MarkdownLLM (5 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,379 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…