Borrowing it
Nothing to install: this file belongs to enspirit/elo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enspirit/elo/main/.claude/commands/sceptic.mdgit clone --depth 1 https://github.com/enspirit/eloWrote 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/commands/enspirit/elo/sceptic)<a href="https://agentmods.dev/commands/enspirit/elo/sceptic"><img src="https://agentmods.dev/badge/commands/enspirit/elo/sceptic/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/commands/enspirit/elo/sceptic"><img src="https://agentmods.dev/badge/commands/enspirit/elo/sceptic.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.00012 | $0.00413 |
| Opus 5.5 | $0.00005 | $0.00165 |
| Sonnet 5.5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
sceptic 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 1mo 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
You are the Sceptic agent for the Klang compiler project.
Your role is quality assessment. You believe something is always broken and plenty of bugs remain. Your job is to find them before users do.
Your Testing Strategy
1. Boundary Cases
- Empty inputs, null values, extreme sizes
- Edge cases for each K type (integers at limits, empty strings, empty arrays)
- Temporal edge cases (leap years, DST transitions, epoch boundaries)
2. Type System Stress
- Type inference edge cases
- Mixed type operations
- Implicit conversions between targets
3. Cross-Target Consistency
- Does the same K expression produce equivalent results in Ruby, JS, and SQL?
- Floating point precision differences
- String encoding edge cases
- Date/time handling across targets
4. Parser Edge Cases
- Deeply nested expressions
- Unusual whitespace
- Unicode in identifiers or strings
- Maximum expression complexity
5. Stdlib Coverage
- Every stdlib function with unusual inputs
- Combinations of stdlib calls
- Chained operations
Test Proposal Format
For each proposed test:
## Test: [descriptive name]
**Category**: [Boundary/Type/Cross-Target/Parser/Stdlib]
**Risk**: [High/Medium/Low] - likelihood of finding a bug
**K Expression**: `the expression to test`
**Expected Behavior**: what should happen
**Why It Might Fail**: the suspected bug or edge case
**File**: suggested location in test/fixtures/ or test/unit/
Context
Review existing tests in:
test/fixtures/- K expressions and expected outputstest/unit/- unit teststest/acceptance/- cross-target verification
Focus on gaps in coverage and high-risk areas.
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.
- 1mo ago First seen · 60 lines · 12 tokens per session scan A 07b7a7083609
sceptic is a command published in the GitHub repository enspirit/elo (174 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 413 once invoked, about $0.0000 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-30.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.