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 agents/solana-foundation/templates/template-metadatagit clone --depth 1 https://github.com/solana-foundation/templatesWrote 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/agents/solana-foundation/templates/template-metadata)<a href="https://agentmods.dev/agents/solana-foundation/templates/template-metadata"><img src="https://agentmods.dev/badge/agents/solana-foundation/templates/template-metadata.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.00000 | $0.00517 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
template-metadata 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Metadata
Template metadata is generated from template package.json files.
Source Of Truth
The source of truth is each template directory's package.json. The generator reads template roots from root package.json under repokit.groups; do not maintain a separate hard-coded group list in docs.
Community templates belong under community/ unless a maintainer asks for another root.
Generated outputs are:
templates.jsonTEMPLATES.md.github/workflows/templates.json
Automatic Generation
pnpm generate runs tsx scripts/generate.ts && automd.
The generator:
- Reads root
package.jsonfor configuredrepokit.groupsandrepository.name. - Scans direct child directories in each configured group.
- Treats a child directory as a template only when it has a
package.json. - Reads template metadata from that
package.json. - Builds each template path as
<group>/<template-directory>. - Builds each template ID from root
repository.nameand the template path. - Sets each image path to
<group>/<template-directory>/og-image.png. - Sorts templates alphabetically by
nameinside each group. - Writes grouped metadata to
templates.json. - Writes a generated Markdown list to
TEMPLATES.md. - Writes a sorted flat path list to
.github/workflows/templates.jsonfor CI.
automd runs after metadata generation and updates README automation blocks, such as the contributors section.
CI also runs generation. Pull requests get a generated metadata preview, and pushes to main can auto-commit regenerated templates.json, TEMPLATES.md, and .github/workflows/templates.json when they change.
Metadata Fields
The generator requires these fields before including a template:
name: unique template package name.description: short summary for listings.keywords: searchable tags.
These fields are also used when present and are expected by the contributor guide for template listings:
displayName: readable name shown in template UIs.usecase: category label.
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.
- 3d ago First seen · 72 lines · 0 tokens per session scan A c5fae09f533a
template-metadata is an agent published in the GitHub repository solana-foundation/templates (106 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 517 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.