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/avksp/agent-lifecycle-kit/audit-agent-plannpx skills add avksp/agent-lifecycle-kit --skill audit-agent-plangit clone --depth 1 https://github.com/avksp/agent-lifecycle-kitWrote 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/avksp/agent-lifecycle-kit/audit-agent-plan)<a href="https://agentmods.dev/skills/avksp/agent-lifecycle-kit/audit-agent-plan"><img src="https://agentmods.dev/badge/skills/avksp/agent-lifecycle-kit/audit-agent-plan.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.1 | $0.00030 | $0.00653 |
| Opus 5 | $0.00015 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
audit-agent-plan 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 5d 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.
Audit agent plan
Use this skill for independent review of a candidate specification or agent-ready plan. The default action is audit only.
Inputs
Read the developer overview first, then the specification, plan manifest, write-set contract, worker DAG, acceptance checklist, evidence plan, budget profile, and previous review if this is a revision.
Review matrix
Check every item for:
- traceability from requirement to acceptance criterion, workstream, evidence, and final audit gate;
- SDD tier correctness;
- missing clarification or unsafe assumption;
- architecture, security, performance, data, browser, release, or external environment risks;
- exact ownership and forbidden writes;
- dependency DAG correctness and parallel safety;
- validation commands that are executable, scoped, bounded, and sufficient;
- context and token budget fit for small and large context hosts;
- deterministic SDD tier resolution evidence or a justified higher-tier override;
- plan/freeze/run artifact separation;
- adapter neutrality and absence of project-specific assumptions unless the target project explicitly owns them.
- optional Review Mesh scope: any blocking multi-review requirement must be off by default, provider-neutral, token/resource capped, phase-scoped, and backed by assignment/result/synthesis/quorum evidence routes.
When available, run agent-lifecycle plan completeness-check --manifest <plan.manifest.json> and treat agent-plan-completeness-validation.v1 blockers
as deterministic pre-audit findings. For freeze gates that opt in to structural
enforcement, also check agent-lifecycle plan check --require-completeness.
For Markdown-only plan packages or plan folders, use the cookbook path in
docs/guides/lifecycle-cookbook.md and docs/guides/code-review-workflows.md
to keep the review draft-only until a real ALK plan is frozen.
Verdicts
READY_TO_FREEZE: no open Medium or High finding; freeze inputs are complete.CHANGES_REQUIRED: the plan can be corrected within the current intent.BLOCKED: external authority or missing product decision prevents a safe plan.REOPEN_REQUIRED: a frozen plan needs contract, ownership, or intent changes.
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.
- 5d ago First seen · 78 lines · 30 tokens per session scan A ca29a0ffe9bc
audit-agent-plan is a skill published in the GitHub repository avksp/agent-lifecycle-kit (18 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 653 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-30.
Other skills, from other repositories
edgeone skill scanner
Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描…
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
agent-review
Critically review a Stencila agent and suggest improvements. Use when asked to review, audit, critique, evaluate, or improve an agent directory or AGENT.md file. Covers frontmatter validation, system instruction quality, configuration correctness, and adherence to the Agent schema.
performing-cryptographic-audit-of-application
A cryptographic audit systematically reviews an application's use of cryptographic primitives, protocols, and key management to identify vulnerabilities such as weak algorithms, insecure modes, hardco.
aws-security-audit
AWS security auditing — IAM users/roles/policies, CloudTrail API events, security posture analysis. Use when auditing IAM permissions, investigating security incidents, checking MFA compliance, or tracing API activity in CloudTrail.
Website Audit
Comprehensive website auditing skill using Lighthouse, PageSpeed Insights, and web performance APIs to audit performance, accessibility, SEO, best practices, and security.