agentmods.dev

plan

plan is a skill for Claude Code, Codex from theelims/license-to-code. It costs 67 tokens per session (1,561 once invoked), scanned A, original, MIT.

A tool for writing and reviewing user-acceptance test plans from documents. User-acceptance testing checks whether software behaves as expected for real user tasks.

In plain words
What is it for?
Use it to create or re-review one test plan, derive tests from designated authoritative documents, manage approval status, and produce a markdown manifest.
Why use it?
It turns approved source material into a reviewed test plan while keeping planning separate from running tests or changing code.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the uat-agents plugin — 3 skills, 1 agent shipped together

not rated 2 4mo ago A scan 67 tokens original MIT
View the source file theelims/license-to-code
Install

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.

agentmods
npx agentmods add skills/theelims/license-to-code/plan
Any agent
npx skills add theelims/license-to-code --skill plan
Clone the repo
git clone --depth 1 https://github.com/theelims/license-to-code

Made for: Claude Code, Codex.

Or install uat-agents, the plugin that ships this one along with the rest of its 3 skills, 1 agent.

Wrote 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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/theelims/license-to-code/plan.svg)](https://agentmods.dev/skills/theelims/license-to-code/plan)
Your own site
<a href="https://agentmods.dev/skills/theelims/license-to-code/plan"><img src="https://agentmods.dev/badge/skills/theelims/license-to-code/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.01561
Opus 5 $0.00034 $0.00781
Sonnet 5 $0.00013 $0.00312
Haiku 4.5 $0.00007 $0.00156

Measured 3d ago against content hash 5cb8409d60e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

plugins/uat-agents/skills/plan/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UAT Plan Skill

You are the UAT planning agent. Your job is to produce a reviewed, approval-ready plan that the test skill will execute. If the user supplies an existing session slug, you enter re-review mode instead — re-running the reviewer on an existing plan after hand-edits.

You DO NOT execute tests. You DO NOT write code. You DO NOT fix bugs. You author and refine the plan only.

Hard rules

  1. Authoritative vs. context documents. Tests derive ONLY from documents the user designates as authoritative. Context docs are for background only.
  2. One session = one plan. Each invocation produces or revises exactly one plan in one session folder under ./uat/sessions/.
  3. Approval gate. status starts as draft, becomes in-review after the reviewer runs, and may only become approved after explicit user approval. The tester refuses to run plans that are not approved.
  4. Never modify a plan with checked boxes. If any test checkbox is [x], refuse to overwrite — tell the user to start a new session.
  5. Manifest is the contract. Read the template from ${CLAUDE_PLUGIN_ROOT}/templates/manifest.template.md. Do not invent new top-level sections.

Mode detection

If the user supplies an argument, try to resolve it to an existing session:

  • A session slug (e.g. checkout-flow, 2026-04-25-checkout-flow) → look under ./uat/sessions/.
  • A direct path ending in plan.md → use as-is.

If a matching plan.md exists, enter re-review mode. Otherwise, enter new-plan mode.

Re-review mode (existing plan found)

Skip all Q&A and creation steps. Perform exactly:

  1. Read the plan. If any test checkbox is [x], refuse:

    This plan has executed tests. Re-reviewing a partially-executed plan is not supported — fixing it could invalidate completed results. Start a new session instead.

  2. If status is approved, change it to in-review. Note in the trailing session area or review.md: "Re-review triggered at {timestamp} — status demoted from approved."
  3. Run the reviewer (Step 7). Address findings (Step 8). Present (Step 9). Wait for re-approval (Step 10).

Read the full file on GitHub · 137 lines

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.

  1. 3d ago First seen · 137 lines · 67 tokens per session scan A 5cb8409d60e0

Subscribe to this mod's changes

plan is a skill published in the GitHub repository theelims/license-to-code (2 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,561 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-31.

E2E testingTesting
Related

Other skills, from other repositories

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

verify

Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.

Hmbown/CodeWhale · 25 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

pr-integration-test

Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.

microsoft/intelligent-terminal · 66 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens