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 AleksandarBisevac/claude-plugins --skill no-silent-passgit clone --depth 1 https://github.com/AleksandarBisevac/claude-pluginsWrote 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/aleksandarbisevac/claude-plugins/no-silent-pass)<a href="https://agentmods.dev/skills/aleksandarbisevac/claude-plugins/no-silent-pass"><img src="https://agentmods.dev/badge/skills/aleksandarbisevac/claude-plugins/no-silent-pass/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/aleksandarbisevac/claude-plugins/no-silent-pass"><img src="https://agentmods.dev/badge/skills/aleksandarbisevac/claude-plugins/no-silent-pass.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.00143 | $0.02802 |
| Opus 5 | $0.00072 | $0.01401 |
| Sonnet 5 | $0.00029 | $0.00560 |
| Haiku 4.5 | $0.00014 | $0.00280 |
Grade A, and why
no-silent-pass 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No silent pass
Two halves of one rule. Code must not produce normal-looking output when something went wrong, and a check must not look green while asserting nothing. Both fail the same way: everything reports fine and nobody learns anything for months.
This repo's test suite is the --selftest block inside each file, printing N/M cases passed.
Everything below is about those cases and the code they guard.
Fail loud
- Give success and failure distinct sentinels. If the error path writes the same value the
success path writes, failed runs read as complete.
except Exception: status = "READY"is the shape to look for. - When you catch, either recover meaningfully or make the failure visible — raise, or return
a distinguishable value. A
return/continue/fallback insideexceptthat produces normal-shaped output is where silent corruption lives. x = x or defaultis a bug whenever0,Falseor""are meaningful. Usex if x is not None else default. Reserve theorform for empty containers.- A no-op on unexpected input is silent corruption. Skipping a key you do not recognise, or
continue-ing past a record you cannot parse, with no error and no count, leaves the caller believing the operation applied. - Filtering down to empty must never read as "all clear." When a selector, rule set or work list narrows to nothing, an "evaluated everything, found no problems" path reports a perfect result while checking nothing. Say that the set was empty.
- Validate every precondition before the first mutation. A write that half-applies and then raises leaves the caller's state corrupted even though the exception was correct. Where that is not possible, stage on a copy and commit after.
- Do not discard the real output on a non-zero exit. A runner that returns only stderr when
returncode != 0loses the answer for tools that exit non-zero by design and write their result to stdout — which is exactly what this repo's own validators and gates do. - Impose a total order before serializing. Iterating a
setemits a different order per process, so a regenerated file is the same data reshuffled and the real change drowns in noise.
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 · 189 lines · 143 tokens per session scan A 807bcd5f47d9
no-silent-pass is a skill published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 143 tokens to every session and 2,802 once invoked, about $0.0007 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 skills, from other repositories
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
python-patterns
Python idioms — type hints, dataclasses, async/await, generators, pytest, common pitfalls. Activate when writing or reviewing Python code.
litestar-testing
Auto-activate for test.py, conftest.py, litestar.testing, TestClient, AsyncTestClient, createtestclient, createasynctestclient, anyio, Guard mocks, DI overrides, or handler tests. Not for generic pytest.
python-testing
Python testing patterns with pytest including unit tests, integration tests, fixtures, mocking, and coverage. Use when writing Python tests.
Unit Test Scaffold (Python/pytest)
Generate Python/pytest unit test skeletons from specifications.