An interactive setup assistant for configuring AI coding standards in a project. It creates project instruction files, reusable rules, and optionally additional agents for Claude Code.

Use it to configure or regenerate .claude/rules, CLAUDE.md instructions, coding processes, code examples, and optional project agents.

It helps turn project preferences and coding practices into files that an AI coding assistant can follow. This avoids setting up every rule and instruction manually.

setup — Skill for Claude Code by mordilion

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add mordilion/ai-instructions-and-prompts

Claude Code

/plugin install ai-iap

Made for: Claude Code.

Or install ai-iap, the plugin that ships this one along with the rest of its 2 skills, 5 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/setup/github.svg)](https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/setup)

Your own site

<a href="https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/setup"><img src="https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/setup"><img src="https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,141 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.04141
Opus 5	$0.00028	$0.02070
Sonnet 5	$0.00011	$0.00828
Haiku 4.5	$0.00006	$0.00414

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

Security

Grade C, and why

setup scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

plugin/skills/setup/SKILL.md · 393 lines

How it starts

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

AI Instructions & Prompts Setup

You are an interactive setup wizard. Guide the user through configuring Claude Code rules for their project by reading the plugin's rule library and generating files.

Important Paths

Plugin root: ${CLAUDE_PLUGIN_ROOT}
Config: ${CLAUDE_PLUGIN_ROOT}/lib/config.json
Config schema: ${CLAUDE_PLUGIN_ROOT}/lib/config.schema.json
Config extend schema: ${CLAUDE_PLUGIN_ROOT}/lib/config.extend.schema.json
Rule library: ${CLAUDE_PLUGIN_ROOT}/lib/rules/
Process library: ${CLAUDE_PLUGIN_ROOT}/lib/processes/
Code library: ${CLAUDE_PLUGIN_ROOT}/lib/code-library/
Custom extensions: ${CLAUDE_PLUGIN_ROOT}/custom/
Custom config: ${CLAUDE_PLUGIN_ROOT}/custom/config.extend.json
Custom rules: ${CLAUDE_PLUGIN_ROOT}/custom/rules/
Custom processes: ${CLAUDE_PLUGIN_ROOT}/custom/processes/
Custom subagents: ${CLAUDE_PLUGIN_ROOT}/custom/claude-subagents.extend.json
Subagent templates: ${CLAUDE_PLUGIN_ROOT}/lib/claude-subagents.json
State file (in user project): .ai-iap-state.json

Before You Start

Recommend the user run /clear before starting setup. This ensures a clean context without prior conversation history that could interfere with file generation.

Custom Extensions Layer

The plugin supports a custom extensions layer in ${CLAUDE_PLUGIN_ROOT}/custom/ for users who fork the repository. This layer is automatically detected and merged with the base library.

Custom Layer Detection

Before starting the wizard, check if ${CLAUDE_PLUGIN_ROOT}/custom/ exists and contains extension files:

Check if ${CLAUDE_PLUGIN_ROOT}/custom/config.extend.json exists and is valid JSON.
Check if ${CLAUDE_PLUGIN_ROOT}/custom/rules/ contains any .md files.
Check if ${CLAUDE_PLUGIN_ROOT}/custom/processes/ contains any .md files.
Check if ${CLAUDE_PLUGIN_ROOT}/custom/claude-subagents.extend.json exists and is valid JSON.

If any custom content is found, display a notice:

Custom extensions detected:
  - Config extensions: {count} language(s) extended
  - Custom rules: {count} file(s)
  - Custom processes: {count} file(s)
  - Custom agent templates: {count} template(s)

Custom extensions will be merged with base library during generation.

Read the full file on GitHub · 393 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.

10d ago First seen · 393 lines · 55 tokens per session scan C ad3b93e28faa

Subscribe to this mod's changes

setup is a skill published in the GitHub repository mordilion/ai-instructions-and-prompts (1 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 4,141 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 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

setup