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/testing-and-cigit 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/testing-and-ci)<a href="https://agentmods.dev/agents/solana-foundation/templates/testing-and-ci"><img src="https://agentmods.dev/badge/agents/solana-foundation/templates/testing-and-ci.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.1 | $0.00000 | $0.00379 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
testing-and-ci 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 6d 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
Testing And CI
Use the smallest validation that proves the change, then run broader checks when touching shared tooling or generated metadata.
Local Commands
pnpm generateupdates generated template metadata.pnpm lintchecks template metadata, duplicate names,og-image.png, and formatting.pnpm formatapplies Prettier.pnpm validatechecks generated metadata shape.
Template Checks
For a changed template, prefer validating from a fresh install path when practical. CI uses create-solana-dapp to instantiate templates, install dependencies, and run npm run ci.
Non-community templates tested by CI need a ci script. If a community template has no ci script, make sure its README setup commands still match its actual package scripts.
CI Files
.github/workflows/validate-templates.ymlchecks metadata generation and validation..github/workflows/test-templates.ymlruns template tests across package managers and non-community template paths..github/actions/create-solana-dapp/action.ymlcontains the shared template creation and install flow..github/actions/setup/action.ymlcontrols Node, package manager, Solana, Anchor, Rust, and other tool setup.
Interpreting Failures
- Metadata failures usually mean
pnpm generatewas not run or a templatepackage.jsonis missing fields. - Image failures usually mean
og-image.pngis missing, too large, or not1200x630. npm run cifailures usually mean a tested template is missing aciscript or its CI script no longer matches the template.- Package manager failures can come from dependency engine constraints, lockfile differences, or template package scripts.
- Do not assume an unrelated CI failure is caused by the current PR without reproducing or isolating it.
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.
- 6d ago First seen · 32 lines · 0 tokens per session scan A 741d471c2fea
testing-and-ci 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 379 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
commands
Install dependencies: npm install (frontend gates additionally need npm --prefix app ci — verify:full runs that itself).
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.