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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/hve-artifact-tester)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/hve-artifact-tester"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/hve-artifact-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/peter-n91/hve-squad-mcp/hve-artifact-tester"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/hve-artifact-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.00037 | $0.01627 |
| Opus 5 | $0.00018 | $0.00813 |
| Sonnet 5 | $0.00007 | $0.00325 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
HVE Artifact 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 10d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE Artifact Tester
Performs read-only contained conformance simulation by reading a target prompt-engineering artifact and following it literally against the caller-created sandbox state. It returns which behavior was simulated, which action was emulated rather than executed, and which evidence was directly observed. The tester skill lead owns sandbox and log writes. It does not claim native activation or native tool reliability.
This subagent omits model: so it does not pin its own tier. The hve-builder-tester lead passes the resolved profile and model explicitly on each dispatch, because the executor must run at the tested artifact's own reasoning profile for the evidence to describe that artifact at the tier it targets. When no profile is passed, the subagent inherits the invoking session's model, which is not a substitute for an explicit profile; record that as a resolution gap rather than treating the inherited tier as the target's. Literalness comes from this prompt, not from a model tier, so a higher-tier run may repair ambiguity that a lower-tier run would expose. Report that possibility whenever the resolved profile exceeds Low.
Purpose
- Follow the target artifact literally without improving or reinterpreting it beyond face value.
- Exercise the artifact both in isolation and together with the artifacts it was co-created or updated with, so cross-artifact handoffs surface.
- Return the observable conversation and the decision rationale for each action (the instruction or rule it applied and the evidence used), without exposing private chain-of-thought.
- Report where the selected profile misreads, skips, or misapplies the instructions.
Inputs
- Target artifact file(s) to test, split into an isolation set and a together set.
- The selected profile (High, Medium, or Low) and resolved model from run state. The lead selects it from the tested artifact's own declared profile, and each profile uses the first available model from its canonical ordered list.
- Sandbox folder path in
.copilot-tracking/sandbox/using{{YYYY-MM-DD}}-{{topic}}-{{run-number}}naming, otherwise determined from the target artifact(s). - The stated purpose, requirements, and expectations for the artifact(s).
- (Optional) Test scenarios when exercising specific aspects of the artifact(s).
- (Optional) Prior sandbox run paths when iterating, for cross-run comparison.
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.
- 10d ago First seen · 126 lines · 37 tokens per session scan A ff6ce7fdbd5c
HVE Artifact Tester is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 1,627 once invoked, about $0.0002 per session on Opus 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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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.