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/ceilf6/frontagent/skill-lifecyclenpx skills add ceilf6/FrontAgent --skill skill-lifecyclegit clone --depth 1 https://github.com/ceilf6/FrontAgentWhat 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.00056 | $0.00685 |
| Opus 5 | $0.00028 | $0.00342 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
skill-lifecycle 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Use this skill when the user wants to work on content skills themselves — creating, evaluating, improving, or benchmarking them.
Trigger
- Requests to create a new content skill
- Requests to improve or benchmark an existing skill
- Requests to reduce false positives or false negatives in skill triggering
- Requests to compare the current skill against a revised candidate
Workflow
- Read
references/workflow.mdto choose the right Skill Lab sequence. - Read
references/eval-guidelines.mdbefore creating or editing trigger evals. - If the skill does not exist yet, scaffold a new skill package (e.g.
frontagent skill scaffold <skill-name>). - If the skill does not yet have evals, initialize trigger evals (e.g.
frontagent skill init-evals <skill-name>). - If behavior quality matters, initialize behavior evals (e.g.
frontagent skill init-behavior-evals <skill-name>). - Run a benchmark before making changes (e.g.
frontagent skill benchmark <skill-name>). Use--behaviorwhen behavior evals are available. - When improvement is requested, generate a candidate and compare it with baseline (e.g.
frontagent skill improve <skill-name>). Use--behaviorto include behavior scoring. - Only apply a candidate when the benchmark clearly improves and the user wants promotion (e.g.
frontagent skill promote <skill-name> <candidate-id>or--apply-if-better).
Platform-specific commands listed above use the
frontagent skillCLI. SeeADAPTATION.mdfor how to map these steps to a different platform.
Output Contract
- Keep the user informed of:
- where eval files live
- where candidate skills were written
- whether benchmark scores improved
- Prefer benchmark-backed recommendations over intuition.
- Treat the skill package itself as the artifact under iteration:
SKILL.mdagents/openai.yaml- existing
references/andassets/
Guardrails
- Do not trust starter evals blindly. Encourage editing them toward real prompts before strong conclusions.
- Do not auto-apply candidates unless the user requested it or the command explicitly says to do so.
- Do not silently broaden a skill's scope just to improve trigger rate.
- Prefer preserving existing references/assets over inventing new file paths.
What ships with it
4 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.
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.
- 2d ago First seen · 67 lines · 56 tokens per session scan A 9cd76f1fa823
skill-lifecycle is a skill published in the GitHub repository ceilf6/FrontAgent (117 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 685 once invoked, about $0.0003 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-30.
Other skills, from other repositories
maintain-model-list
Maintain the supported LLM model list: add a new model, or run routine maintenance to verify availability and discover new models worth adding. Use when the user asks to add/support a model, update the model list, or check model availability.
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.
agent-spec-wiki
Use when initializing, checking, enriching, or reviewing agent-spec code live wiki pages, sourcefiles trace, or Rust architecture inventory.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.