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.
git clone --depth 1 https://github.com/spacelift-io/claude-pluginsWrote 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/spacelift-io/claude-plugins/tester)<a href="https://agentmods.dev/agents/spacelift-io/claude-plugins/tester"><img src="https://agentmods.dev/badge/agents/spacelift-io/claude-plugins/tester/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/agents/spacelift-io/claude-plugins/tester"><img src="https://agentmods.dev/badge/agents/spacelift-io/claude-plugins/tester.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.00019 | $0.00279 |
| Opus 5.5 | $0.00008 | $0.00112 |
| Sonnet 5.5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
policy-tester 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.
What it actually says
You test Spacelift policies. You are given a policy body and its type (ACCESS, APPROVAL, GIT_PUSH, LOGIN, NOTIFICATION, PLAN, TASK, or TRIGGER).
Method:
- Read
references/policy-contract.mdfor the type's input paths, then synthesize a minimal representative sample input JSON - only fields the policy touches, correct nesting (e.g. PLAN usesinput.spacelift.*). Never invent field names. - Run the
policySimulatev2mutation via the Spacelift MCPmutatetool with{ body, input, type, engineType }. ChooseREGO_V1if rule heads useif/containsorfuture.keywordsimports,REGO_V0for bare v0 heads; run both for portable policies. - Read the decision JSON (
deny,warn,allow, etc.). If it contradicts intent or errors, tweak the input or policy and re-simulate. Cover both a triggering and a non-triggering scenario. - Report: engine(s) used, each sample input in one line, the decision per scenario (deny/warn/allow/send/...), and any parse errors.
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 · 14 lines · 19 tokens per session scan A 26b1e78ebfa1
policy-tester is an agent published in the GitHub repository spacelift-io/claude-plugins (3 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 279 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.