project-brief

project-brief is a skill for Claude Code from FeiZhuLulu/kimi-code-skills. It costs 35 tokens per session (1,977 once invoked), scanned A, original, MIT.

A read-only guide to the code around a particular feature, bug, module, or folder. It creates a temporary explanation for the current task rather than changing project files.

In plain words
What is it for?
Use it before changing a specific area, such as an authentication module or an API route, when you need focused code navigation.
Why use it?
It helps an agent understand unfamiliar code and local conventions without requiring a full project setup or leaving generated documentation behind.

Skill for Claude Code

Written for Claude Code: arguments in frontmatter. Also seen: mentions subagents; mentions AGENTS.md.

Good fit Use it before changing a specific area, such as an authentication module or an API route, when you need focused code navigation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/feizhululu/kimi-code-skills/project-brief
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 FeiZhuLulu/kimi-code-skills --skill project-brief
Clone the repo
git clone --depth 1 https://github.com/FeiZhuLulu/kimi-code-skills

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 project-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/feizhululu/kimi-code-skills/project-brief/github.svg)](https://agentmods.dev/skills/feizhululu/kimi-code-skills/project-brief)
Your own site
<a href="https://agentmods.dev/skills/feizhululu/kimi-code-skills/project-brief"><img src="https://agentmods.dev/badge/skills/feizhululu/kimi-code-skills/project-brief/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 project-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/feizhululu/kimi-code-skills/project-brief"><img src="https://agentmods.dev/badge/skills/feizhululu/kimi-code-skills/project-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,977 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.00035 $0.01977
Opus 5 $0.00017 $0.00988
Sonnet 5 $0.00007 $0.00395
Haiku 4.5 $0.00003 $0.00198

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

Security

Grade A, and why

project-brief 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.

project-brief/SKILL.md · 227 lines

How it starts

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

Project Brief — Task-Focused Code Navigation

Purpose

Generate a task-focused project brief for a specific module, feature, bug, or directory. This is a lightweight complement to /init:

/init project-brief
Scope Whole project Specific module / feature / directory
Output AGENTS.md (persistent) In-conversation brief (temporary)
Purpose Help AI understand project conventions Help you navigate unfamiliar code for a task
When First time onboarding a project Before modifying a specific area

This skill does not generate AGENTS.md or any persistent files. It produces a focused, in-conversation brief that helps you understand the code around your current task.

Kimi Code Usage

Manual invocation:

/skill:project-brief
/skill:project-brief auth
/skill:project-brief src/api/routes.ts

This skill may be automatically invoked when the user asks to understand a module or navigate unfamiliar code.

Kimi Code Behavior

This skill is read-only.

  • Do not edit, create, delete, format, or initialize files.
  • Do not run /init.
  • Do not generate or modify AGENTS.md.

Input

Target: $target

If $target is empty, ask the user what module, feature, file, directory, or bug they want to understand.

The target can be:

  • A module or package name: auth, user-service, payment
  • A file path: src/api/routes.ts
  • A feature name: login flow, search functionality
  • A bug or error reference: the null pointer in user.ts
  • A directory: src/components/
  • A concept: how caching works

Workflow

1. Identify the Target

Parse the user's input to determine:

  • What: module name, file, feature, or concept
  • Scope: narrow (single file) or broad (entire module)

2. Locate Relevant Files

Prefer tracked files first. Treat the target as a literal string, not a shell expression or regex.

Safe pattern:

git ls-files | rg -i --fixed-strings -- '<literal-target>'

Read the full file on GitHub · 227 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 · 227 lines · 35 tokens per session scan A 98c99c27ad39

Subscribe to this mod's changes

project-brief is a skill published in the GitHub repository FeiZhuLulu/kimi-code-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,977 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.

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

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