agentmods.dev

planner: Skill for Claude Code

.claude/skills/update-repo/SKILL.md

update-repo is a skill for Claude Code from nickmisasi/planner. It costs 41 tokens per session (922 once invoked), scanned A, original, MIT.

A workflow for changing the planning repository itself, including its skills, templates, hooks, and instruction files.

In plain words
What is it for?
It helps add or revise skills, change templates, modify automated hooks, and update files such as CLAUDE.md or AGENTS.md.
Why use it?
It provides a defined way to update the tools and rules that guide work in the repository.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

This is nickmisasi/planner's own configuration. It tells Claude Code how to work on planner itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything planner configures →

not rated 5repo 4mo ago A scan 41 tokens original MIT
View source ↗ nickmisasi/planner
Reuse

Borrowing it

Nothing to install: this file belongs to nickmisasi/planner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nickmisasi/planner/main/.claude/skills/update-repo/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nickmisasi/planner

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 update-repo

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickmisasi/planner/update-repo/github.svg)](https://agentmods.dev/skills/nickmisasi/planner/update-repo)
Your own site
<a href="https://agentmods.dev/skills/nickmisasi/planner/update-repo"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/update-repo/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 update-repo

Your own site · 80×15
<a href="https://agentmods.dev/skills/nickmisasi/planner/update-repo"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/update-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 922 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.
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.00041 $0.00922
Opus 5 $0.00020 $0.00461
Sonnet 5 $0.00008 $0.00184
Haiku 4.5 $0.00004 $0.00092

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

Security

Grade A, and why

update-repo 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.

.claude/skills/update-repo/SKILL.md · 87 lines

How it starts

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

Iterate on the planning repository itself — add skills, update templates, modify hooks, refine CLAUDE.md, or evolve the repo structure.

Instructions

When the user invokes /update-repo, follow these steps:

1. Understand the Change

Ask the user (or infer from conversation context) what they want to change. Common categories:

  • New skill: Add a new slash command
  • Update skill: Modify an existing skill's behavior
  • Template change: Add or update a scaffolding template
  • Hook change: Add or modify Claude Code hooks in .claude/settings.json
  • Structure change: Modify the repo's directory conventions or file formats
  • CLAUDE.md update: Update agent instructions, rules, or workflows
  • AGENTS.md update: Update universal agent instructions

2. Read Current State

Before making changes, read the relevant files to understand what exists:

  • For new/updated skills: read .claude/skills/ directory listing and the relevant SKILL.md file(s)
  • For template changes: read templates/ directory listing and the relevant template(s)
  • For hook changes: read .claude/settings.json
  • For structure changes: read CLAUDE.md (especially the Repository Structure and File Format Conventions sections)
  • For CLAUDE.md/AGENTS.md changes: read the full file

3. Propose the Change

Before modifying anything, present the proposed change to the user:

  • What file(s) will be created or modified
  • A summary of the change
  • Any ripple effects (e.g., "adding this skill means we should also update the skills table in CLAUDE.md")

Wait for user approval before proceeding.

4. Implement the Change

Make the changes. For each type:

New skill:

  1. Create .claude/skills/<skill-name>/SKILL.md with frontmatter (name, description) following the pattern of existing skills
  2. Add the skill to the Available Skills table in CLAUDE.md
  3. Update AGENTS.md if the skill is relevant to non-Claude agents
  4. Update README.md skills table

Updated skill:

  1. Edit the SKILL.md file in .claude/skills/<skill-name>/
  2. Update CLAUDE.md if the skill's purpose or interface changed

Read the full file on GitHub · 87 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. 8d ago First seen · 87 lines · 41 tokens per session scan A ecd466c8b035

Subscribe to this mod's changes

update-repo is a skill published in the GitHub repository nickmisasi/planner (5 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 922 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.

Building agents
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens