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 tae0y/python-project-template --skill template-upstreamgit clone --depth 1 https://github.com/tae0y/python-project-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/tae0y/python-project-template/template-upstream)<a href="https://agentmods.dev/skills/tae0y/python-project-template/template-upstream"><img src="https://agentmods.dev/badge/skills/tae0y/python-project-template/template-upstream/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/tae0y/python-project-template/template-upstream"><img src="https://agentmods.dev/badge/skills/tae0y/python-project-template/template-upstream.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.00000 | $0.01328 |
| Opus 5.5 | $0.00000 | $0.00531 |
| Sonnet 5.5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
template-upstream 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 155 lines · 0 tokens per session scan A 83ad7082a77e
template-upstream is a skill published in the GitHub repository tae0y/python-project-template (14 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,328 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-09-01.
Other skills, from other repositories
agent-whole-qa
A coordinator for testing an entire application and sending failures to separate development and testing agents. It repeats repair and regression rounds rather than writing code or tests itself.
agent-mvp
An execution workflow for building a minimum viable product, meaning the smallest complete version of a product that can be tested with users. It reads approved plans, assigns development and testing in order, and coordinates fixes until the planned checks pass.
plan-mvp
A planning workflow for defining a complete minimum viable product from the beginning. It gathers decisions in planning mode and records the product, interface, project, data, and API documents for a later implementation workflow.
plan-feature
A guided planning workflow for adding an incremental feature to an existing product. It compares the requested change with current code and documented requirements before recording the work for implementation.
agent-feature
An execution workflow for implementing a previously planned feature. It reads the approved requirements and coordinates development, testing, and targeted rechecks without redesigning the feature.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).