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 skills add sruja-ai/sruja --skill sruja-harnessgit clone --depth 1 https://github.com/sruja-ai/srujaWrote 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/skills/sruja-ai/sruja/sruja-harness)<a href="https://agentmods.dev/skills/sruja-ai/sruja/sruja-harness"><img src="https://agentmods.dev/badge/skills/sruja-ai/sruja/sruja-harness/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/skills/sruja-ai/sruja/sruja-harness"><img src="https://agentmods.dev/badge/skills/sruja-ai/sruja/sruja-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 19 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00058 | $0.00628 |
| Opus 5 | $0.00029 | $0.00314 |
| Sonnet 5 | $0.00012 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
sruja-harness 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 11d 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
Sruja Harness Skill
Universal verification adapter — works with any coding, bugfix, or review skill.
Quick Start
-
Install alongside other skills:
npx skills add https://github.com/sruja-ai/sruja --skill sruja-harness npx skills add https://github.com/sruja-ai/sruja --skill sruja-architecture -
Use with any skill: This skill does not generate code. It verifies output from other skills.
-
Before marking a task done:
sruja verify-task --profile coding -r . -
On verify failure:
sruja agent record -r . \ -c "<task context>" \ -H "<what was tried>" \ -o failed \ -g "<correction for next time>"
Rules
- Always verify before done — Run
sruja verify-taskwith the appropriate profile before declaring a task complete. - Profile selection:
coding— New features, refactors (default)bugfix— Bug fixes (use--fileto target the bug location)review— Pre-merge review of changesarch— Architecture/DSL changes
- On failure: Record a correction learning before retrying.
- On success: Optionally record an affirmation learning ("what worked").
Integration with Other Skills
Coding Skill (e.g. /build) → sruja-harness verify → record_learning → done
This skill does not replace coding skills — it ensures their output passes Sruja's architecture gates.
Profiles
| Profile | Verifies |
|---|---|
coding |
lint repo.sruja + just check (or make check) + drift |
bugfix |
focus --file + just check (or make check) + intent check |
review |
review -f json + intent check + drift |
arch |
lint repo.sruja + drift + intent check + review |
References
- docs/HOST_AGENT_INTEGRATION.md — Full integration contract
- docs/plans/AGENT_DELIVERY_PLAN.md — Delivery roadmap
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.
- 11d ago First seen · 70 lines · 58 tokens per session scan A f69820df717b
sruja-harness is a skill published in the GitHub repository sruja-ai/sruja (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 628 once invoked, about $0.0003 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 skills, from other repositories
validate
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
mandu-mcp-verify
An automatic verification workflow for the Mandu project that runs after edits, generated files, or before a commit. It checks generated behavior, architecture rules, code quality, and project structure in parallel.
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
specflow
Spec-driven development with executable contracts.
specflow-simulate
Simulates end-to-end usage of a Specflow story across multiple personas and divergent routes to discover gaps, edge cases, and unhandled branches BEFORE the story is built — then proposes each finding as a concrete story addition (new REQ, negative-path AC, Gherkin branch, or journey step). This is the high-value…
testing
Test generation and coverage analysis. Activated when the user says "create tests", "write tests", "test this", "check coverage", "add test", "missing tests", "TDD", or wants to create or improve tests.