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/rios0rios0/guide/scaffold-python-packagegit clone --depth 1 https://github.com/rios0rios0/guideWhat 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.00000 | $0.01023 |
| Opus 5 | $0.00000 | $0.00511 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
scaffold-python-package 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 yesterday.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a new Python package following PEP 621, PDM, Black/isort/Flake8, type hints, and Loguru logging.
For detailed Python conventions, refer to the Python rule. For testing patterns, refer to the Testing rule. For Makefile setup, refer to the CI/CD rule.
Directory Structure
<project>/
├── <package_name>/
│ ├── __init__.py
│ └── main.py
├── tests/
│ ├── __init__.py
│ └── test_main.py
├── examples/
│ └── example_usage.py
├── Dockerfile
├── pyproject.toml
└── README.md
Step-by-Step
1. Initialize with PDM
mkdir <project> && cd <project>
pdm init
2. Configure pyproject.toml (PEP 621)
[project]
name = "package-name"
version = "0.1.0"
description = "Brief description of the package"
readme = "README.md"
requires-python = ">=3.10"
license = {text = "MIT"}
authors = [
{name = "Author Name", email = "[email protected]"},
]
dependencies = []
[project.optional-dependencies]
dev = [
"black",
"isort",
"flake8",
"pytest",
"loguru",
]
[build-system]
requires = ["pdm-backend"]
build-backend = "pdm.backend"
[tool.black]
line-length = 120
[tool.isort]
profile = "black"
line_length = 120
[tool.flake8]
max-line-length = 120
3. Create the package module
# <package_name>/__init__.py
"""Package description."""
__version__ = "0.1.0"
# <package_name>/main.py
from loguru import logger
def main() -> None:
"""Entry point for the package."""
logger.info("Starting application")
4. Add type hints everywhere
All functions must have type hints on parameters and return types:
def process_data(input_data: list[str], max_items: int = 10) -> dict[str, int]:
"""Process the input data and return counts."""
result: dict[str, int] = {}
for item in input_data[:max_items]:
result[item] = result.get(item, 0) + 1
return result
5. Set up logging with Loguru
Always use Loguru -- NEVER use the standard logging module or print():
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.
- yesterday First seen · 161 lines · 0 tokens per session scan A 3021a0c104c8
scaffold-python-package is a command published in the GitHub repository rios0rios0/guide (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,023 tokens. 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
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
to-issues
Create one Linear issue per slice from an existing scope.json. Run standalone to (re)create issues without rerunning the full Plan phase. Falls back to docs/issues.md if Linear MCP is unavailable.
sdlc-modernize
Industrial legacy system modernization, Strangler Fig migrations, monolith decoupling, and zero-downtime schema evolution.
sdlc-test
Generate and run multi-tiered enterprise test suites (Unit, Integration, E2E, Contract, Load/k6, Chaos, and Fuzz testing).
sdlc-review
Anytime — Industry-standard code review. Spawns 3 parallel reviewers (compliance, bugs, history). Posts inline comments via gh pr comment.