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 commands/ivanlutsenko/awac-ai-agent-plugins/init-projectgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWhat 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 | $0.00013 | $0.00803 |
| Opus 5 | $0.00006 | $0.00402 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00080 |
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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize New Project
Initialize new project with essential structure: $ARGUMENTS
Instructions
-
Project Analysis and Setup
- Parse the project type and framework from arguments:
$ARGUMENTS - If no arguments provided, analyze current directory and ask user for project type and framework
- Create project directory structure if needed
- Validate that the chosen framework is appropriate for the project type
- Parse the project type and framework from arguments:
-
Base Project Structure
- Create essential directories (src/, tests/, docs/, etc.)
- Initialize git repository with proper .gitignore for the project type
- Create README.md with project description and setup instructions
- Set up proper file structure based on project type and framework
-
Framework-Specific Configuration
- Web/React: Set up React with TypeScript, Vite/Next.js, ESLint, Prettier
- Web/Vue: Configure Vue 3 with TypeScript, Vite, ESLint, Prettier
- Web/Angular: Set up Angular CLI project with TypeScript and testing
- API/Express: Create Express.js server with TypeScript, middleware, and routing
- API/FastAPI: Set up FastAPI with Python, Pydantic models, and async support
- Mobile/React Native: Configure React Native with navigation and development tools
- Desktop/Electron: Set up Electron with renderer and main process structure
- CLI/Node: Create Node.js CLI with commander.js and proper packaging
- Library/NPM: Set up library with TypeScript, rollup/webpack, and publishing config
-
Development Environment Setup
- Configure package manager (npm, yarn, pnpm) with proper package.json
- Set up TypeScript configuration with strict mode and path mapping
- Configure linting with ESLint and language-specific rules
- Set up code formatting with Prettier and pre-commit hooks
- Add EditorConfig for consistent coding standards
-
Testing Infrastructure
- Install and configure testing framework (Jest, Vitest, Pytest, etc.)
- Set up test directory structure and example tests
- Configure code coverage reporting
- Add testing scripts to package.json/makefile
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.
- 2d ago First seen · 79 lines · 0 tokens per session scan A 52be7d219794
init-project is a command published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 803 once invoked, about $0.0001 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.