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/armanzeroeight/fastagent-plugins/setup-projectgit clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/commands/armanzeroeight/fastagent-plugins/setup-project)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/setup-project"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/setup-project.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 | $0.00013 | $0.01686 |
| Opus 5 | $0.00006 | $0.00843 |
| Sonnet 5 | $0.00003 | $0.00337 |
| Haiku 4.5 | $0.00001 | $0.00169 |
Grade A, and why
setup-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 today.
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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Python Project
Initialize a new Python project with proper structure and configuration.
Context
- Current directory: !
pwd - Existing files: !
ls -la
Your Task
Create a well-structured Python project with appropriate configuration based on the project type.
Arguments
$1: Project name (required) - will be used for directory and package names$2: Project type (optional) -app,library, orcli(defaults toapp)
Steps
-
Determine project type from arguments or ask user:
app: Application (web service, script, etc.)library: Reusable library for distributioncli: Command-line tool
-
Create project structure based on type:
For applications (app):
project-name/ ├── src/ │ └── project_name/ │ ├── __init__.py │ ├── main.py │ └── config.py ├── tests/ │ ├── __init__.py │ └── test_main.py ├── pyproject.toml ├── .gitignore └── README.mdFor libraries (library):
project-name/ ├── src/ │ └── project_name/ │ ├── __init__.py │ └── core.py ├── tests/ │ ├── __init__.py │ └── test_core.py ├── docs/ │ └── index.md ├── pyproject.toml ├── .gitignore └── README.mdFor CLI tools (cli):
project-name/ ├── src/ │ └── project_name/ │ ├── __init__.py │ ├── cli.py │ └── commands/ │ └── __init__.py ├── tests/ │ ├── __init__.py │ └── test_cli.py ├── pyproject.toml ├── .gitignore └── README.md -
Create pyproject.toml with UV/PEP 621 configuration:
[project] name = "project-name" version = "0.1.0" description = "Project description" readme = "README.md" requires-python = ">=3.9" authors = [ {name = "Your Name", email = "[email protected]"} ] dependencies = [] [project.optional-dependencies] dev = [ "pytest>=7.0.0", "black>=23.0.0", "mypy>=1.0.0", "ruff>=0.1.0", ] [build-system] requires = ["hatchling"] build-backend = "hatchling.build"
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.
- today First seen · 316 lines · 13 tokens per session scan A 5c88c7a1807e
setup-project is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,686 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-09-03.
Other commands, from other repositories
create-python-tests
Command "create-python-tests" from codeready-toolchain/tarsy, covering writing tests for python llm service, running tests, from project root, from llm-service/ directory and critical rules.
prepare-dataset
Analyse a raw data file (CSV, JSON, JSONL, TSV, Parquet) and generate a complete Python script scripts/dataset/ .py that inherits from BaseDatasetPreparer and transforms the file into a JSONL dataset ready for fine-tuning with Unsloth.
refactor-py-sdk
Command to refactor Python SDK.
setup:python
Set up a new Python project with quality tools and Claude framework integration.
test-zh
中文生成测试.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.