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 neuromechanist/research-skills --skill init-projectgit clone --depth 1 https://github.com/neuromechanist/research-skillsWrote 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/neuromechanist/research-skills/init-project)<a href="https://agentmods.dev/skills/neuromechanist/research-skills/init-project"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/init-project/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/neuromechanist/research-skills/init-project"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/init-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 143 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00136 | $0.01891 |
| Opus 5 | $0.00068 | $0.00945 |
| Sonnet 5 | $0.00027 | $0.00378 |
| Haiku 4.5 | $0.00014 | $0.00189 |
Grade A, and why
init-project 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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Initialization with Vibe Rules Templates
Initialize new projects with a structured development environment for Codex, Claude Code, Copilot, and optionally Cursor. The templates enforce consistent development practices: real testing (no mocks), atomic commits, documentation-driven development, and continuous rule improvement.
When to Use
- Starting a new project from scratch
- Adding cross-agent structure to an existing project
- Setting up .rules/ and .context/ directories for a project that lacks them
- Migrating a project to vibe-rules conventions
Partial-init detection: if AGENTS.md or .rules/ already exists, this is not a fresh init. Inventory what exists first; scaffold only the missing pieces (never overwrite an existing AGENTS.md or customized rule), and use the update-rules skill instead when the ask is to refresh existing files against newer templates. For understanding an existing codebase before documenting it, run codebase-onboarding first and reuse its report for the architecture map in Step 4.
Template Structure
The plugin bundles all templates under templates/:
templates/
agents/ # Shared agent templates
AGENTS.md # Main cross-agent instructions file
claude/ # Claude Code adapter templates
CLAUDE.md # Imports AGENTS.md, then holds Claude-only guidance
rules/ # Detailed rule references
testing.md # NO MOCK testing policy
git.md # Version control standards
python.md # Python/UV standards
code_review.md # PR review toolkit
documentation.md # MkDocs standards
ci_cd.md # GitHub Actions setup
self_improve.md # Rule evolution
serena_mcp.md # Code intelligence tools
context/ # Documentation scaffolding
plan.md # Task tracking with phases
ideas.md # Design concepts
research.md # Technical explorations
scratch_history.md # Failed attempts and lessons
decisions/ # Architecture Decision Records
README.md # ADR convention (numbering, statuses, when to write one)
0000-template.md # Template for new ADRs (do not edit)
config/ # Development configuration
pre-commit # Ruff pre-commit hook (Python)
pyproject.toml # Python project config
pytest.ini # Pytest config
mkdocs.yml # Documentation config
gitignore-template # Common ignores
github/ # CI/CD templates
workflows/
test.yml # Test pipeline
docs.yml # Documentation deployment
release.yml # Release automation
cursor/ # Cursor IDE templates (optional)
.cursorrules # Main cursor config
core_rules/ # Modular .mdc rule files
planning/
default/ # Plan-based development workflow
advanced-taskmaster/ # Complex project task management
What ships with it
3 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.
- 12d ago First seen · 167 lines · 136 tokens per session scan A 597a79f7d150
init-project is a skill published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 9d ago), licensed BSD-3-Clause. It adds 136 tokens to every session and 1,891 once invoked, about $0.0007 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-30.
Other skills, from other repositories
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
3d-essentials
Use when working with 3D-specific systems — materials, lighting, shadows, environment, global illumination, fog, LOD, occlusion culling, and decals in Godot 4.3+.
addon-development
Use when creating Godot editor plugins — EditorPlugin, @tool scripts, custom inspectors, and dock panels.
ai-navigation
Use when implementing AI movement — NavigationAgent2D/3D, steering behaviors, behavior trees, and patrol patterns.
animation-system
Use when implementing animations — AnimationPlayer, AnimationTree, blend trees, state machines, sprite animation, and code-driven animation.
assets-pipeline
Use when importing and managing assets — image compression, 3D scene import, audio formats, resource formats, and import configuration.