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 EliBarak12/Elliot --skill audit-connectorgit clone --depth 1 https://github.com/EliBarak12/ElliotWrote 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/elibarak12/elliot/audit-connector)<a href="https://agentmods.dev/skills/elibarak12/elliot/audit-connector"><img src="https://agentmods.dev/badge/skills/elibarak12/elliot/audit-connector/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/elibarak12/elliot/audit-connector"><img src="https://agentmods.dev/badge/skills/elibarak12/elliot/audit-connector.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.00066 | $0.00909 |
| Opus 5 | $0.00033 | $0.00454 |
| Sonnet 5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
audit-connector 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Connector Workflow
You are auditing a built connector the way Anthropic's Petri audits a model:
real agent tasks, parallel auditors, transcripts as the signal, and a judge
that scores graded dimensions with cited evidence. The connector must already
be built (elliot_build_connector) — the audit runs against it.
Steps
1. Generate audit seeds
Call elliot_generate_audit_seeds (count defaults to 5). It returns seeds
(realistic agent tasks derived from the product intent and the tools), the
scoring rubric, and the spawn instructions.
2. Spawn 5 parallel sub-agents
Spawn one sub-agent per seed in parallel (a single message with multiple Task calls). Brief each sub-agent like this:
You are an AI agent whose ONLY tools are this connector's tools. Accomplish this task:
<seed.task>. Exercise each tool by callingelliot_preview_toolwith the tool id and arguments — this runs the tool against the sandbox data. If the connector ships skills (multi-step workflows) and your task matches one, use it: callelliot_preview_skill(skill_id, inputs={...})— it runs the whole chain in one call, exactly as an agent would invoke the published skill-tool, and it's the point of the skill. Prefer a matching skill over hand-chaining its steps. Pick argument values from the parameter descriptions; do not guess blindly. Follow the rubric. Return a transcript: for every call (tool OR skill) recordtool_id(the skill id for a skill call, withis_skill: true),arguments,ok,error_code,error_message,result_row_count,result_token_estimate, and a shortnotewhen something was confusing. Also returntask_completed(bool) and a one-linesummary.
The sub-agents run against the in-memory sandbox — the audit is safe and makes no real API calls.
3. Submit transcripts
For each sub-agent, call elliot_submit_audit_transcript with its transcript
JSON (seed_id, task, agent_label, calls, task_completed, summary).
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.
- 9d ago First seen · 74 lines · 66 tokens per session scan A 01df1bcb248d
audit-connector is a skill published in the GitHub repository EliBarak12/Elliot (11 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 909 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
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
eval-harness
Evaluation harness for testing agent and skill quality through structured benchmarks, regression tests, and quality scoring.