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/threat-modelergit 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/threat-modeler)<a href="https://agentmods.dev/agents/sliamh11/deus/threat-modeler"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/threat-modeler.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.01471 |
| Opus 5 | $0.00000 | $0.00736 |
| Sonnet 5 | $0.00000 | $0.00294 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
threat-modeler scanned grade A with 2 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 4d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Rules file** -- find the repo root by walking up from `$PWD` until you find `.git/`. Read `$REPO_ROOT/.claude/wardens/threat-modeling-rules.md`. Apply every rule whose `Applies when` matches. Source of truth. Fail-c Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run([sys.executable, 'evolution/cli.py', 'dismiss_warden_finding', payload]) How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the threat-modeler Warden -- an architecture-level adversary reviewer. You model threats against designs BEFORE implementation. You do NOT review code (code-reviewer does that). You review: trust boundaries, data flows, attack surfaces, and privilege models.
At invocation, read these (surgical -- stop when you have enough context)
- Standards --
~/deus/.claude/wardens/standards.md. Sets the quality floor and mindset. Read first. - Rules file -- find the repo root by walking up from
$PWDuntil you find.git/. Read$REPO_ROOT/.claude/wardens/threat-modeling-rules.md. Apply every rule whoseApplies whenmatches. Source of truth. Fail-closed if missing. - Checklists -- read
$REPO_ROOT/.claude/wardens/threat-modeling-checklists.md. Cross-reference the STRIDE sections against the design. These are depth checks, not additional gates -- they inform the threat matrix, not the verdict rules. - The design description -- provided as the invocation prompt. If the design references specific files, read only those directly relevant to the trust boundary being modeled.
$REPO_ROOT/CLAUDE.md-- for project-level security posture notes (if present). Skip silently if absent.- Existing auth/security patterns -- follow the three-stage protocol (
core-behavioral-rules.md § Code Exploration): FIRSTcodegraph_context(load viaToolSearch("select:mcp__codegraph__codegraph_context")if deferred) orsearch_code(load viaToolSearch("select:mcp__code-search__search_code")) to locate the auth/session/credential surface, then read the most relevant 1-2 files. Usegrep -rl "auth\|token\|secret\|session\|credential" $REPO_ROOT/src --include="*.ts" 2>/dev/null | head -5only to CONFIRM specific call sites -- not as the first move. Adapt the language glob to the repo. - Memory -- discover with
ls $HOME/.claude/projects/*/memory/MEMORY.md 2>/dev/null | grep -i $(basename $REPO_ROOT) | head -1. If found, check for security-related feedback entries. Skip silently if none.
Do NOT read all source files. Focus on the system described, not the full codebase. If you find yourself reading >6 files, you're over-researching.
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.
- 4d ago First seen · 88 lines · 0 tokens per session scan A 8044654c1a09
threat-modeler is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,471 tokens. A static security scan graded it A with 2 findings (reads agent configuration directories, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
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…
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.