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 leynier/python-template --skill project-workflowgit clone --depth 1 https://github.com/leynier/python-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/leynier/python-template/project-workflow)<a href="https://agentmods.dev/skills/leynier/python-template/project-workflow"><img src="https://agentmods.dev/badge/skills/leynier/python-template/project-workflow/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/leynier/python-template/project-workflow"><img src="https://agentmods.dev/badge/skills/leynier/python-template/project-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00346 |
| Opus 5.5 | $0.00023 | $0.00138 |
| Sonnet 5.5 | $0.00012 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
project-workflow 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.
What it actually says
Project Workflow
Use the generated project as the source of truth for its enabled layers.
Workflow
- Read
.copier-answers.yml,pyproject.toml, andreadme.mdbefore changing architecture or commands. - Preserve the
srclayout, public entry points, Python version, dependency groups, and existing user changes. - Add dependencies with
uv addoruv add --group dev; do not hand-edit the lockfile. - Keep secrets out of source control. Document required values in
.env.exampleand load them through the generated settings layer when present. - Add or update tests alongside behavior changes.
- Run
uv sync --all-groups,uv run ruff check .,uv run ruff format --check ., anduv run pytestbefore delivery. - If the project was created from a Git reference and needs upstream fixes, use
copier updateonly from a clean worktree and review the resulting diff carefully.
Entry Points
- For a library, verify imports and its public API.
- For a CLI, run its generated console command and a representative option.
- For an API or interface, start it locally and exercise the health or primary route.
- For MCP, agents, RAG, inference, training, or deployment, use the additional generated skill when present.
What ships with it
1 file 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.
- 1mo ago First seen · 26 lines · 58 tokens per session scan A 32b039ac4c2f
project-workflow is a skill published in the GitHub repository leynier/python-template (37 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 346 once invoked, about $0.0002 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-30.
Other skills, from other repositories
deepeval
DeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent, tool-using workflow, multi-turn chatbot, RAG pipeline, or LLM app; add evals; generate datasets or goldens; use deepeval generate; use deepeval test run; send results to Confident AI…
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
llm-patterns
AI-first application patterns, LLM testing, prompt management.
creating-online-evaluations
Author continuously-running online evaluations in PostHog AI observability, grounded in real failure modes you've identified. Use when the user wants evaluations that automatically score new generations or whole traces going forward — "create an eval to catch X", "continuously check that responses do Y", "turn these…
playwright-e2e-testing
This skill should be used when the user asks to "create an E2E test", "write a Playwright scenario", "add a Playwright test", "generate e2e tests", "create actions and checks", "write playwright checks", "add scenario for feature", or when modifying, reviewing, or debugging Playwright E2E test files in the workspace.