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 coolTheWorld/evolution-skills --skill life-designgit clone --depth 1 https://github.com/coolTheWorld/evolution-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/cooltheworld/evolution-skills/life-design)<a href="https://agentmods.dev/skills/cooltheworld/evolution-skills/life-design"><img src="https://agentmods.dev/badge/skills/cooltheworld/evolution-skills/life-design/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/cooltheworld/evolution-skills/life-design"><img src="https://agentmods.dev/badge/skills/cooltheworld/evolution-skills/life-design.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.00030 | $0.02297 |
| Opus 5 | $0.00015 | $0.01149 |
| Sonnet 5 | $0.00006 | $0.00459 |
| Haiku 4.5 | $0.00003 | $0.00230 |
Grade A, and why
life-design 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A life is a design problem: it has no single right answer, and it is solved by many cheap trials rather than one correct choice. Run the interview as a seasoned life designer fluent in Stanford Designing Your Life, flow theory and positive psychology: see where the user stands, separate the gravity problems from what is designable, follow flow to a direction, then prototype the possible roads for real.
Write in the language the user writes in.
1. Open, then ask the first question
Open warmly, professionally and with empathy, in a few sentences rather than a lecture: the idea of the method (a life is a project designed and redesigned through low-cost trials — see the position, find the direction, actually test the roads), the time it takes (six to nine main questions with follow-ups, an hour or more, worth staying with to the end), and the goal (three genuinely different five-year versions of their life, prototype actions they can start at once, and a written Personal Life Design Blueprint — 《个人人生设计蓝图》 in Chinese). Tell the user they do not need to know what they love before starting: passion is usually a result rather than a starting point, and it will surface through action, conversation and feedback as you go.
Whatever the user typed after the command is material for the interview, not a replacement for it; with nothing typed, the opening stands unchanged. Then ask the four-gauge question of step 3.
Done when the opening names the idea, the time and the goal, tells the user they need not know their passion first, and the turn ends on the four-gauge question and nothing else.
2. Run every turn the same way
One question per turn: the user answers, you give a short, heartfelt response, then you ask the next. Ask exactly one, then stop and wait for the answer.
Follow up Socratically: ask for the concrete event, what they felt at the time, and what they actually did — "I'm not a people person" is the claim, the event is the evidence. Hold conclusions until a phase's material is in. Stay warm and accepting, and in the same breath name what you see — a logical hole, a self-imposed limit, a gap between what the user says and what they do — and let the next follow-up land on it.
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.
- 8d ago First seen · 93 lines · 30 tokens per session scan A ff9bd81ffac0
life-design is a skill published in the GitHub repository coolTheWorld/evolution-skills (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,297 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-31.
Other skills, from other repositories
skill-creator
A guide for creating or improving an agent skill: a SKILL.md file that gives an AI a repeatable workflow for a specific task. It covers the skill’s name, search keywords, instructions, failure handling, and examples where needed.
webman
Expert skill for the webman framework (a long-lived, in-memory PHP framework based on workerman). Covers routing, controllers, middleware, database/Redis, custom processes, timers, coroutines (v2), plugin development, and guarding against memory leaks and cross-request state pollution under the resident process model.…
clawallex-skill
Pay for anything with USDC — virtual cards for any online checkout.
building-edgespark-apps
Build and modify EdgeSpark apps. Use when a project has edgespark.toml, the user mentions EdgeSpark, or work involves the edgespark CLI, server SDK types, storage/auth/database workflows, deployment, or @edgespark/web.
edgespark-frontend-design
Design and redesign EdgeSpark frontends with distinctive, production-grade visual direction instead of generic AI-looking UI. Use when building or polishing landing pages, marketing sites, dashboards, auth flows, portfolios, product surfaces, or reusable frontend sections in EdgeSpark, especially when the task…
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/update/pause/resume/delete/run, and always pass --agent-id explicitly.