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 TheSmuks/ai-project-template --skill setupgit clone --depth 1 https://github.com/TheSmuks/ai-project-templateWrote 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/thesmuks/ai-project-template/setup)<a href="https://agentmods.dev/skills/thesmuks/ai-project-template/setup"><img src="https://agentmods.dev/badge/skills/thesmuks/ai-project-template/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/thesmuks/ai-project-template/setup"><img src="https://agentmods.dev/badge/skills/thesmuks/ai-project-template/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.00026 | $0.05055 |
| Opus 5.5 | $0.00010 | $0.02022 |
| Sonnet 5.5 | $0.00005 | $0.01011 |
| Haiku 4.5 | $0.00003 | $0.00505 |
Grade A, and why
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 1mo 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 — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Setup Skill
Guides the agent (or user) through project initialization from the ai-project-template. This skill replaces the static SETUP_GUIDE.md with an interactive, multi-step workflow that lets adopters select which features to include.
When to Use
Invoke this skill when:
- Starting a new project from the
ai-project-template - Adopting template conventions into an existing project
- Running
/setupin an OMP session for a new repo - User says "set up this project" or "initialize from template"
- User pastes the bootstrap prompt: "Set up this project from the ai-project-template. Read SETUP_GUIDE.md and follow the interactive setup."
One-Liner Trigger
When a user pastes this prompt, invoke this skill immediately:
Set up this project from the ai-project-template. Read SETUP_GUIDE.md and follow the interactive setup.
The skill will:
- Read
SETUP_GUIDE.mdfor structured guidance - Detect the context (greenfield vs existing repo)
- Ask targeted questions about language, build tools, and features
- Generate and customize files
- Verify the setup
- Present a post-setup orientation explaining what was installed
Prerequisites
Before running this skill:
- Ensure you're in a git repository (initialized or about to be)
- Verify you have write permissions to create files
- Read
SETUP_GUIDE.md— it contains the authoritative step definitions
Feature Groups
The setup workflow operates on opt-in feature groups. Each group can be accepted or declined. The skill asks, doesn't assume.
| Group | Default | Includes |
|---|---|---|
| Core Docs | On (required) | AGENTS.md, ARCHITECTURE.md, CONTRIBUTING.md, README.md, CHANGELOG.md |
| CI Workflows | On | commit-lint, changelog-check, blob-size-policy, ci.yml, branch-lint |
| Agent Config | On | .omp/agents/ (code-reviewer, adr-writer, changelog-updater) |
| OMP Extensions | On | .omp/rules/, .omp/hooks/, .omp/tools/ |
| OMP Skills | On | .omp/skills/ (cut-release, merge-to-main, template-guide) |
| Dev Container | Off | .devcontainer/ configuration |
| Code Quality | On | .editorconfig, code style thresholds |
| ADR Process | On | docs/decisions/, initial ADR template |
| Git Ignore | On | Language-specific .gitignore patterns |
| CODEOWNERS | Off | CODEOWNERS file |
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.
- 1mo ago First seen · 612 lines · 26 tokens per session scan A 2e5b44b77db7
setup is a skill published in the GitHub repository TheSmuks/ai-project-template (8 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 5,055 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
template-shell
Shell helper scripts for the template research framework. Covers system health checks, local CI reproduction, uv bootstrap, and rsync backup/restore contracts under scripts/shell/.
ai
This skill should be used when the user asks about "AI development", "AI coding", "AI assistant", "CLAUDE.md", "AI context", "AI guidelines", "code generation", "AI workflow", "AI review", "AI configuration", or needs guidance on configuring AI assistants and AI-assisted development workflows.
docs
This skill should be used when the user asks about "documentation", "README", "CHANGELOG", "CONTRIBUTING", "ADR", "architecture decision record", "changelog format", "keep a changelog", "doc comments", "API documentation", or needs guidance on project documentation requirements.
observability
This skill should be used when the user asks about "observability", "logging", "metrics", "tracing", "monitoring", "structured logging", "log format", "log levels", "distributed tracing", "OpenTelemetry", "health checks", or needs guidance on implementing observability and monitoring requirements.
quality
This skill should be used when the user asks about "code quality", "formatting", "linting", "lint rules", "code style", "error handling", "unsafe code", "documentation comments", "doc comments", "rustfmt", "prettier", "eslint", "clippy", or needs guidance on code quality enforcement and configuration.
release
This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump", "release notes", or needs guidance on release workflows and version management.