plannotator-setup-goal

plannotator-setup-goal is a skill for Claude Code from jellydn/my-ai-tools. It costs 21 tokens per session (798 once invoked), scanned A, original, MIT.

A guided discovery tool that turns an idea into a goal package containing confirmed requirements and codebase findings.

In plain words
What is it for?
It is for defining feature goals, users, behavior, success measures, scope, edge cases, and constraints before implementation.
Why use it?
It reduces guesswork by restating the goal, interviewing the user one question at a time, and examining the existing code where needed.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions Codex; built for cline; mentions OpenCode.

Good fit It is for defining feature goals, users, behavior, success measures, scope, edge cases, and constraints before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jellydn/my-ai-tools/plannotator-setup-goal
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.

Any agent
npx skills add jellydn/my-ai-tools --skill plannotator-setup-goal
Clone the repo
git clone --depth 1 https://github.com/jellydn/my-ai-tools

Made for: Claude Code.

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 plannotator-setup-goal

README.md
[![agentmods](https://agentmods.dev/badge/skills/jellydn/my-ai-tools/plannotator-setup-goal/github.svg)](https://agentmods.dev/skills/jellydn/my-ai-tools/plannotator-setup-goal)
Your own site
<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/plannotator-setup-goal"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/plannotator-setup-goal/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.

agentmods 80×15 button for plannotator-setup-goal

Your own site · 80×15
<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/plannotator-setup-goal"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/plannotator-setup-goal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 798 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00021 $0.00798
Opus 5 $0.00010 $0.00399
Sonnet 5 $0.00004 $0.00160
Haiku 4.5 $0.00002 $0.00080

Measured 10d ago against content hash 7ff681d84424, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

plannotator-setup-goal 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 10d 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.

configs/amp/plugins/my-ai-tools-skills/skills/plannotator-setup-goal/SKILL.md · 93 lines

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.

Setup Goal

Turn an idea into a goal package at goals/<slug>/ through structured discovery, user interview, and codebase exploration.

Phases

1. Rearticulate

State back what the user wants in your own words. If the conversation already has rich context, summarize it. If the goal is bare or vague, do minimal shallow exploration of the codebase to ground your understanding. Keep it to 2-3 sentences. Wait for the user to confirm or correct before continuing.

2. Interview (grill me)

Interview the user such that you can derive every "fact" this goal should produce, & until you reach a complete shared understanding of the desired outcomes. The following question areas should help you determine facts about the outcome.

  • What the feature/change is
  • Who it's for
  • What problem it solves
  • What behavior changes
  • What success looks like
  • What's in and out of scope (The most important area to determine facts)
  • What edge cases to consider
  • What constraints or precedent apply

Ask questions one at a time, waiting for feedback before continuing. For each question, provide your recommended answer. Use the question/answer tool if available.

If a question can be answered by exploring the codebase, explore the codebase instead of asking.

Stop when confident you can describe the goal outcome facts.

3. Fact Sheet

A fact is a simple description of each outcome of a goal. It should be easily testable and verifiable. A fact may describe the function of a specific feature or aspect of a system. A fact may determine specific UI and UX. Again, a fact is literally anything that can be tested and verified in automated or manual testing. Keep fact language simple. In a way, a fact sheet is a design spec, but less verbose & using language the human user can easily visualize & rationalize.

Create the goal directory and write goals/<slug>/facts.md — a flat list of bulleted facts. Each fact is one line. Add a minimal note only when the fact can't be stated clearly on its own.

Read the full file on GitHub · 93 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. 10d ago First seen · 93 lines · 21 tokens per session scan A 7ff681d84424

Subscribe to this mod's changes

plannotator-setup-goal is a skill published in the GitHub repository jellydn/my-ai-tools (120 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 798 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-08-30.