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/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/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/alexeyshishin/as-skill/code-skeptic"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/code-skeptic.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.00046 | $0.00307 |
| Opus 5.5 | $0.00018 | $0.00123 |
| Sonnet 5.5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
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 today.
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.
- today Changed · +10 lines · +46 tokens per session 6caad84ee6d8
- 1mo ago First seen · 27 lines · 0 tokens per session scan A 24f7dad06d9b
skeptic is an agent published in the GitHub repository alexeyshishin/as-skill (5 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 307 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
skill-files-reviewer
Reviews supporting files (scripts, references, assets) that sit next to a SKILL.md. Use proactively after adding or changing any file in skills/ / other than SKILL.md itself.
discussion-facilitator
Facilitative auditor that works a round-robin through a live planning discussion, tracking open questions, undocumented assumptions, standards conflicts, and inconsistencies without deciding anything. Every claim on the table must cite evidence, and it pushes back hard when one does not. Use when a planning…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
behavioral-analyst
Analyzes the runtime behavior of a specified codebase focus area — data flow, error propagation, state management, and integration boundaries. Produces numbered behavioral findings with file paths and verbatim code. Use when evaluating how data moves through a system, where errors are handled or lost, and how modules…