Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SongshGeo/Python-Project-Templatenpx agentmods add skills/songshgeo/python-project-template/setup-projectWrote 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/songshgeo/python-project-template/setup-project)<a href="https://agentmods.dev/skills/songshgeo/python-project-template/setup-project"><img src="https://agentmods.dev/badge/skills/songshgeo/python-project-template/setup-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/songshgeo/python-project-template/setup-project"><img src="https://agentmods.dev/badge/skills/songshgeo/python-project-template/setup-project.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.00069 | $0.00690 |
| Opus 5.5 | $0.00028 | $0.00276 |
| Sonnet 5.5 | $0.00014 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-project
Guided, one-stop initialization for a new project created from this template. Run the steps in order, confirming with the user where noted. If a step's tool is missing, stop and tell the user how to install it rather than guessing.
1. Gather metadata
Ask the user (conversationally) for:
- Project name — used as the package/distribution name.
- Project description — one short sentence.
Do not proceed until both are non-empty.
2. Configure project files (non-interactive)
Run the config script with the collected values:
uv run python scripts/configure_project.py --name "<name>" --description "<description>"
This updates [project] in pyproject.toml, fills the ${project_name}
placeholder in .github/workflows/release-please.yml, rewrites README.md, and
clears CHANGELOG.md.
3. Install dependencies
uv sync --all-extras
(or make setup for the guided make path). uv is required — if it is missing,
point the user at curl -LsSf https://astral.sh/uv/install.sh | sh.
4. Set up pre-commit
uv run pre-commit install
uv run pre-commit run --all-files
Report any hook failures; offer to fix them.
5. Offer to reset git history
Ask whether the user wants a clean history for their new project. Only if they say yes:
rm -rf .git && git init && git add -A && git commit -m "chore: initial commit from template"
Never reset history without explicit confirmation.
6. Install the recommended external skills
npx skills@latest add SongshGeo/skills
The CLI is interactive: tell the user to select the recommended set documented in
.claude/recommended-skills.md (grill-me, grilling, to-prd, to-issues, tdd,
diagnosing-bugs, prototype, domain-modeling, codebase-design,
improve-codebase-architecture, code-review, handoff) and to enable them for
Claude Code. This is optional — the user can skip it.
7. Initialize the memory bank
Using the project's stated vision, draft initial content for:
memory-bank/architecture.md— intended module layout and boundaries.memory-bank/model-design.md— the core entities/data shapes, if known.
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 · 90 lines · 69 tokens per session scan E 175675275387
setup-project is a skill published in the GitHub repository SongshGeo/Python-Project-Template (8 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 690 once invoked, about $0.0003 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.