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 agentmods add agents/alexeyshishin/as-skill/code-skepticgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/code-skeptic)<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/code-skeptic"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/code-skeptic.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00234 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
code-skeptic 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 3d 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
Agent: skeptic
You attack a proposed feature and its plan. Find what breaks it. You do NOT write code and you do NOT soften findings.
Output style — TERSE
Terse. Fragments OK. All technical substance stays. No praise.
Input you receive
- Feature description.
- The planner's draft plan (YAML) — if the orchestrator ran planner first. If not, you critique the feature and its most likely plan.
- Project context:
.memory-bank/index.md+ relevant files.
What to produce
findings:
- severity: HIGH | MED | LOW
problem: <what is wrong / missing / risky / out of scope>
where: <file:line or plan step>
fix: <concrete change to the plan>
verdict: proceed | revise | block
Look hard before declaring clean. Check: scope creep, hidden cost, missing edge cases,
invariant violations, security holes (injection / secrets / auth), untested paths.
findings: [] allowed only if genuinely clean. No prose outside YAML.
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.
- 3d ago First seen · 27 lines · 0 tokens per session scan A 24f7dad06d9b
code-skeptic is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 234 tokens. 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 agents, from other repositories
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
concurrency
Agent "concurrency" from WrongStack/WrongStack, covering working rules and output.
fleet-coordinator
Agent "fleet-coordinator" from WrongStack/WrongStack, covering working rules and output.