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.
npx agentmods add skills/kissrosecicd-hub/agents-evolution/project-bootstrapnpx skills add kissrosecicd-hub/agents-evolution --skill project-bootstrapgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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.
[](https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/project-bootstrap)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/project-bootstrap"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/project-bootstrap.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00807 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
project-bootstrap 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Bootstrap
Триггеры: "новая директория", "новый проект", "начни работу", "создай AGENTS.md", "project bootstrap", "инициализируй проект", "новая папка проект", "подготовь проект", "настрой правила для проекта", "init project rules"
Контекст
ИИ начинает работу в новой директории (проект, папка, репозиторий). Нужно чтобы любой CLI/IDE загрузил правила из ~/AGENTS.md.
Алгоритм
Шаг 1: Проверка
- Есть ли
AGENTS.md,QWEN.md,CLAUDE.md,GEMINI.md,.cursorrulesв текущей папке? - Есть ли
~/AGENTS.md(Linux/macOS) или%USERPROFILE%\AGENTS.md(Windows)?
Шаг 2: Действие
Если ~/AGENTS.md НЕ существует:
→ Создай минимальный ~/AGENTS.md с правилами #1 (секреты), #2 (думай умно), #3 (✅😈), ссылкой на полный файл если появится.
Если в проекте уже есть AGENTS.md:
→ Не перезаписывай. Открой, прочитай. Если нет ссылки на ~/AGENTS.md → добавь в начало: # Главный файл правил: ~/AGENTS.md. Если уже есть → ничего не делай.
Если в проекте нет AGENTS.md: → Создай все применимые файлы (см. таблицу ниже).
Шаг 3: Создание файлов
| CLI/IDE | Файл | Содержимое |
|---|---|---|
| Qwen Code | <project>/.qwen/AGENTS.md или <project>/QWEN.md |
Ссылка на ~/AGENTS.md |
| Claude Code | <project>/CLAUDE.md |
Ссылка на ~/AGENTS.md |
| Codex | <project>/.codex/AGENTS.md |
Ссылка на ~/AGENTS.md |
| Gemini CLI | <project>/GEMINI.md |
Ссылка на ~/AGENTS.md |
| Cursor | <project>/.cursorrules |
Ссылка на ~/AGENTS.md |
| Иные | <project>/AGENTS.md |
Ссылка на ~/AGENTS.md |
Содержимое каждого файла:
# Project Rules
Следуй глобальным правилам: `~/AGENTS.md`
Почему это работает
- Мини-файл ~10 слов (~75 токенов) — дёшево, всегда в контексте
- Кроссплатформенно:
~для Linux/macOS,%USERPROFILE%для Windows - Кросс-CLI: создаёшь все форматы — любой инструмент подхватит правила
- Ссылка, не копия — при обновлении
~/AGENTS.mdвсе проекты получают актуальные правила
Примеры
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.
- 6d ago First seen · 61 lines · 0 tokens per session scan A dbce05eb42f6
project-bootstrap is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 807 tokens. 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…