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-authoringgit 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-authoring)<a href="https://agentmods.dev/agents/solana-foundation/templates/template-authoring"><img src="https://agentmods.dev/badge/agents/solana-foundation/templates/template-authoring.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.00375 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
template-authoring 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 4d 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
Template Authoring
Use this when adding or changing a template.
Required Files
Each template directory scanned by repokit.groups must include:
package.jsonog-image.png
Community templates belong under community/<template-name>/ unless a maintainer asks for another root.
Package Metadata
Template package.json files should include these listing fields:
namedisplayNamedescriptionusecasekeywords
Follow existing templates for conventions. Keep descriptions concise because they are shown in listings.
The generator and linter currently enforce name, description, and non-empty keywords. The contributor guide also expects displayName and usecase for complete template listings.
Configuration And Secrets
- Do not commit
.envfiles, private keys, seed phrases, API tokens, or personal wallet addresses. - Use
.env.examplefor required configuration. - Use placeholders for sensitive values; safe defaults such as
SOLANA_CLUSTER=devnetare okay. - Avoid dependencies or setup scripts that require hidden local state.
Generated Metadata
Run pnpm generate after adding, removing, renaming, or changing metadata for a template.
Do not manually patch templates.json, TEMPLATES.md, or .github/workflows/templates.json unless the generator itself is being changed and you are checking expected output.
Agent And MCP Templates
Templates that expose agent, MCP, wallet, signing, or transaction automation behavior need clear README notes for:
- What the agent can access.
- What authentication is required.
- Which actions require explicit user approval.
- Whether the template can sign messages, submit transactions, trade, or move funds.
- How users revoke access.
Avoid unsafe defaults. Wallet or transaction automation should not run without a deliberate user action.
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.
- 4d ago First seen · 52 lines · 0 tokens per session scan A 62601fe42c75
template-authoring is an agent published in the GitHub repository solana-foundation/templates (106 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 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.