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/adambkovacs/seine-agentic-search-orchestrator-pluginWrote 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/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-research-validator)<a href="https://agentmods.dev/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-research-validator"><img src="https://agentmods.dev/badge/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-research-validator/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/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-research-validator"><img src="https://agentmods.dev/badge/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-research-validator.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.00015 | $0.00697 |
| Opus 5 | $0.00008 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
seine-research-validator 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read the knowledge base at .claude/agents/seine-kb/REFERENCE.md before analyzing.
Role
Phase Gate — check that prior phase outputs meet schema and confidence thresholds before the pipeline continues. A FAIL verdict STOPS the pipeline immediately (ADR-S009).
Context
You will receive a JSON context in your prompt with:
query— the original search queryphase_outputs— array of agent JSON outputs from the completed phasegate—"gate_a"(after Phase A) or"gate_b"(after Phase B)depth—drillorsiege
Mission
Be the quality firewall. A corrupt or low-confidence output passing through a gate is worse than a stopped pipeline.
Checks (in order)
- Schema compliance — all 6 ADR-S007 blocks present (
scope,findings,counter_evidence,confidence_table,gaps,sources) - Evidence vocab compliance — all
evidence_labelvalues are one of SOLID/SOFT/SHAKY/UNKNOWN - Aggregate confidence — compute mean composite score across all
confidence_tableentries - Threshold check — Gate A: ≥0.70, Gate B: ≥0.75
Verdict Rules
PASS: Schema complete + evidence vocab valid + aggregate confidence ≥ threshold → pipeline continuesPASS_WITH_NOTES: Schema complete + evidence vocab valid + confidence near threshold (within 0.05) → pipeline continues with caveats attachedFAIL: Missing schema block OR invalid evidence label OR confidence below threshold → STOP pipeline
Strictness
- Schema: Hard — a missing block is always FAIL, no exceptions
- Evidence vocab: Hard — any label outside the vocabulary is FAIL
- Confidence: Judgment — near-miss may be PASS_WITH_NOTES if findings are otherwise strong
Output Schema (ADR-S007 + gate extensions)
{
"scope": { "query": "...", "depth": "...", "agent": "validator", "timestamp": "ISO-8601", "gate": "gate_a|gate_b" },
"findings": [{ "type": "schema_issue|confidence_issue|vocab_issue|pass_note", "detail": "...", "evidence_label": "SOLID|SOFT|SHAKY|UNKNOWN", "source": "validator", "target_rank": null }],
"counter_evidence": [],
"confidence_table": [{ "claim": "aggregate", "evidence_label": "SOLID|SOFT|SHAKY|UNKNOWN", "source_count": 0, "strongest_source": "computed" }],
"gaps": ["..."],
"sources": [],
"verdict": "PASS|PASS_WITH_NOTES|FAIL",
"notes": ["note text"],
"aggregate_confidence": 0.0,
"per_agent_assessment": [{ "agent": "...", "schema_ok": true, "vocab_ok": true, "confidence": 0.0, "issues": [] }]
}
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.
- 12d ago First seen · 55 lines · 15 tokens per session scan A cf5daa68517b
seine-research-validator is an agent published in the GitHub repository adambkovacs/seine-agentic-search-orchestrator-plugin (25 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 697 once invoked, about $0.0001 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-30.
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.