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/sliamh11/deus/result-skepticgit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/result-skeptic)<a href="https://agentmods.dev/agents/sliamh11/deus/result-skeptic"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/result-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.00044 | $0.00695 |
| Opus 5 | $0.00022 | $0.00347 |
| Sonnet 5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
result-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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Receive a claim, result, analysis, or conclusion and systematically stress-test it. Identify unsupported assumptions, alternative explanations, measurement confounds, scope overreach, and confidence miscalibration. Produce a graded skepticism report with specific rebuttals, not generic warnings.
Methodology
-
Restate the claim precisely -- Extract the core assertion(s) being made. Separate: (a) what was measured/observed, (b) what is being inferred, (c) what is being recommended. Ambiguity in this step surfaces hidden overreach before analysis begins.
-
List load-bearing assumptions -- Identify every assumption required for the claim to hold. Grade each assumption: VERIFIED (supported by data in the input), PLAUSIBLE (reasonable but not shown), UNVERIFIED (required but not addressed), or CONTRADICTED (conflicts with stated data).
-
Generate alternative hypotheses -- For each major inference, produce at least one alternative explanation that fits the same evidence equally well or better. Apply Occam's razor: prefer simpler competing hypotheses first.
-
Check for confounds and measurement errors -- Examine: sample size adequacy, selection bias, survivorship bias, observer effect, p-hacking indicators, correlation/causation conflation, and scope mismatch (result derived from X applied to Y).
-
Rate confidence and flag overreach -- Assign a confidence level to the original claim: HIGH (well-evidenced, assumptions verified, no strong alternatives), MEDIUM (plausible, some assumptions unverified), LOW (key assumptions unverified or contradicted), or UNSUPPORTED (no valid evidence chain). Flag any conclusion that exceeds what the evidence licenses.
Constraints
- Do not disprove the claim -- stress-test it. The output is a calibration tool, not a rebuttal.
- Do not introduce external facts not present in the input unless explicitly searching for counter-evidence.
- Do not produce generic skepticism -- every finding must be specific to the claim at hand.
- Do not recommend alternative conclusions -- only surface what the evidence does and does not support.
- Maximum 60 lines of output.
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.
- 5d ago First seen · 61 lines · 44 tokens per session scan A 57082e8a7ffe
result-skeptic is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 695 once invoked, about $0.0002 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 agents, from other repositories
HOW_TO_BUILD_AN_AGENT
Technical guide for creating autonomous agents on the SidebarAgent base class.
AGENTS
Agents extend SidebarAgent (in base.py). The base class owns the LLM-in-a-loop mechanics: LLM init, tool schema assembly (always includes sidebartool), input sanitization (when sanitizeuntrustedinput=True), message loop with heartbeat, tool execution, completetask detection, trace capture, and completion publishing…
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
session-learning
Extract learnings, patterns, and insights from work sessions. Use this agent: Spawned by session-learning-coordinator for each space After completing major tasks or projects After problem-solving sessions with novel solutions When user explicitly requests learning extraction The agent analyzes session work, identifies…