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/Da7-Tech/trialWrote 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/plugins/da7-tech/trial/trial)<a href="https://agentmods.dev/plugins/da7-tech/trial/trial"><img src="https://agentmods.dev/badge/plugins/da7-tech/trial/trial/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/plugins/da7-tech/trial/trial"><img src="https://agentmods.dev/badge/plugins/da7-tech/trial/trial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trial 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
{
"name": "trial",
"version": "0.5.3",
"description": "Pre-delivery evidence gate: withhold unsupported completion claims and release only verified results.",
"author": {
"name": "Da7-Tech",
"url": "https://github.com/Da7-Tech"
},
"homepage": "https://github.com/Da7-Tech/trial",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 105 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 12 lines scan A 9b08b5ee7aaf
trial is a plugin published in the GitHub repository Da7-Tech/trial (3 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
rosetta-light
Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails. (lightweight: simpler workflows, smaller models).
coder-eval
Test whether your Claude Code skills actually trigger, and benchmark any coding agent — author, run, and analyze the eval suite that proves it, locally or as a CI gate.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
skraft
skraft SDLC pipeline — agents, skills and instructions for outside-in TDD, Clean Architecture and the RESEARCH→DESIGN→DISTILL→DELIVER engineering pipeline.
god-prompt-mcp
GodPrompt engineering workflows for task routing, TDD, debugging, verification, and progressive disclosure.
supericons
Search, preview, recommend, and retrieve SVG icons by meaning through Supericons MCP.