What is tune-persona?

A project-level persona setup guide that creates or updates an AGENTS.md file, which tells a coding agent how to behave in that project. It covers the agent's role, document standards, decision-making detail, and communication style.

Use it to configure an agent as a particular kind of project partner and set expectations for its documents, decisions, and communication.

It puts project-specific working preferences in one place instead of repeating them in every request. It can also update an existing project's instructions after asking about the desired behaviour.

How kintecus/build configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kintecus/build. 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/kintecus/build/main/.claude/skills/tune-persona/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/kintecus/build

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kintecus/build/tune-persona/github.svg)](https://agentmods.dev/skills/kintecus/build/tune-persona)

Your own site

<a href="https://agentmods.dev/skills/kintecus/build/tune-persona"><img src="https://agentmods.dev/badge/skills/kintecus/build/tune-persona/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/kintecus/build/tune-persona"><img src="https://agentmods.dev/badge/skills/kintecus/build/tune-persona.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 689 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.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.00689
Opus 5	$0.00028	$0.00345
Sonnet 5	$0.00011	$0.00138
Haiku 4.5	$0.00006	$0.00069

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

Security

Grade A, and why

tune-persona 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 9d 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/tune-persona/SKILL.md · 56 lines

How it starts

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

Tune persona

Adjust the agent persona for a specific project by creating or updating the project-level AGENTS.md.

Usage

/tune-persona {project-name}

If no project name is given, ask which active project to tune (check the workspace AGENTS.md for the list).

Workflow

Step 1: Load current state

Read projects/{project-name}/AGENTS.md if it exists (or a legacy CLAUDE.md regular file). If neither, note that we're creating one from scratch.

Also read projects/{project-name}/BRIEF.md and projects/{project-name}/WAYS-OF-WORKING.md for context about the project.

Step 2: Interview

Ask the PM about desired agent behavior. Use what you know from the project docs to suggest defaults. Ask 2-3 questions at a time using AskUserQuestion.

Areas to cover:

Archetype: What kind of PM partner do you need? (senior TPM, product strategist, program manager, builder-operator, or describe your own)
Document standards: What bar should artifacts meet? (Amazon 6-pager precision, lean one-pagers, working notes, mixed depending on audience)
Decision rigor: How thoroughly should decisions be tracked? (every decision logged, key decisions only, lightweight capture in STATUS.md)
Communication style: Tone and audience? (formal/precise, casual/direct, depends on artifact type)

If the project already has an AGENTS.md with a persona, show the current settings and ask what to change rather than re-interviewing from scratch.

Step 3: Generate or update

If no AGENTS.md exists: create one using the templates/PROJECT-AGENTS.md template, populated from interview answers. Add a CLAUDE.md symlink beside it (ln -s AGENTS.md CLAUDE.md) so Claude Code picks it up - it reads nested CLAUDE.md, not nested AGENTS.md.
If AGENTS.md exists: update the relevant sections, preserving any project-specific rules the PM added manually.
If only a legacy CLAUDE.md regular file exists: rename it to AGENTS.md and replace it with a symlink, then update.

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

9d ago First seen · 56 lines · 55 tokens per session scan A 797b472bc598

Subscribe to this mod's changes

tune-persona is a skill published in the GitHub repository kintecus/build (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 689 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.

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

build: Skill for Claude Code