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 skills add vaayne/agent-kit --skill project-setupgit clone --depth 1 https://github.com/vaayne/agent-kitWrote 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/vaayne/agent-kit/project-setup)<a href="https://agentmods.dev/skills/vaayne/agent-kit/project-setup"><img src="https://agentmods.dev/badge/skills/vaayne/agent-kit/project-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.
<a href="https://agentmods.dev/skills/vaayne/agent-kit/project-setup"><img src="https://agentmods.dev/badge/skills/vaayne/agent-kit/project-setup.svg" alt="Reviewed on agentmods" width="80" 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.00199 | $0.01670 |
| Opus 5.5 | $0.00080 | $0.00668 |
| Sonnet 5.5 | $0.00040 | $0.00334 |
| Haiku 4.5 | $0.00020 | $0.00167 |
Grade A, and why
project-setup 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project setup
Apply one baseline to every repository, then add the rules for each stack the repository uses. The target repository owns the result: it pins its own tool versions and installs its own skills. This skill only says what to install and where to get it.
Modes
- Setup applies the baseline to a new repository, or to an existing one when the user asks for the change.
- Audit reports the differences between the repository and the baseline, with file references and a proposed change for each. An audit does not install, generate, format, or move files.
State the mode before you start. If the request is not clear, run an audit.
New and existing repositories
The stack choices in this skill (Vite+, TypeScript 7, TanStack Query, Effect, golangci-lint, PostgreSQL) are defaults for new projects. In an existing repository, keep the established stack, package manager, and documentation layout. Report a stack migration as a proposal; do it only when the user puts it in scope. Read the ADRs and data-ownership rules before you interpret leftover configuration.
Procedure
-
Inspect. Read the existing agent instructions,
git status, and the manifests (package.json,go.mod,mise.toml,prek.toml,dprint.json). Identify the stacks. Record any user edits in the working tree and preserve them.Complete when you know the stacks and which baseline parts already exist.
-
Lay out instructions. Follow layout. Create the root
AGENTS.mdindex and the.agents/rules/files. Keep existing rules that still apply; move them into the matching rule file. -
Install the common tooling and rules. Follow these for every repository:
- tooling: mise and
.mise/tasks, prek, dprint, documd, and e2e. - testing: test policy, tiers, coverage, and enforcement.
- documentation: document layout, figures, and Fumadocs for public docs.
- github: commits, issues, PRs, CI, and Dependabot.
- tooling: mise and
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 145 lines · 199 tokens per session scan A 1af0d1adfdc7
project-setup is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 4d ago), licensed MIT. It adds 199 tokens to every session and 1,670 once invoked, about $0.0008 per session on Opus 5.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-10-13.
Other skills, from other repositories
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.