Huntable-CTI-Studio: Agent for Claude Code

.claude/agents/contract-guardian.md

contract-guardian is an agent for Claude Code from dfirtnt/Huntable-CTI-Studio. It costs 95 tokens per session (740 once invoked), scanned A, original, MIT.

A read-only review agent for checking whether database schemas, configuration, migrations, prompts, and presets still agree with a project's defined contracts.

In plain words
What is it for?
Use it before committing changes to contract-related files, especially model definitions, workflow configuration schemas, migration scripts, and extractor specifications.
Why use it?
It catches mismatches that ordinary code review may miss, such as a database migration that does not match the application models or test schema.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is dfirtnt/Huntable-CTI-Studio's own configuration. It tells Claude Code how to work on Huntable-CTI-Studio itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Huntable-CTI-Studio configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dfirtnt/Huntable-CTI-Studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dfirtnt/Huntable-CTI-Studio/main/.claude/agents/contract-guardian.md
Clone the repo
git clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-Studio

Made for: Claude Code.

Wrote 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.

agentmods badge for contract-guardian

README.md
[![agentmods](https://agentmods.dev/badge/agents/dfirtnt/huntable-cti-studio/contract-guardian/github.svg)](https://agentmods.dev/agents/dfirtnt/huntable-cti-studio/contract-guardian)
Your own site
<a href="https://agentmods.dev/agents/dfirtnt/huntable-cti-studio/contract-guardian"><img src="https://agentmods.dev/badge/agents/dfirtnt/huntable-cti-studio/contract-guardian/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.

agentmods 80×15 button for contract-guardian

Your own site · 80×15
<a href="https://agentmods.dev/agents/dfirtnt/huntable-cti-studio/contract-guardian"><img src="https://agentmods.dev/badge/agents/dfirtnt/huntable-cti-studio/contract-guardian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 740 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.00740
Opus 5 $0.00048 $0.00370
Sonnet 5 $0.00019 $0.00148
Haiku 4.5 $0.00010 $0.00074

Measured 11d ago against content hash 6c5ca04fcf50, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

contract-guardian 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 11d 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.

.claude/agents/contract-guardian.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the contract-drift reviewer for Huntable CTI Studio. Per AGENTS.md, src/config/workflow_config_schema.py and src/database/models.py are contract sources of truth; docs/contracts/*.md hold the extractor specifications. Several other surfaces embed copies or projections of these contracts, and the codebase has no automatic enforcement between them — your job is to catch the drift a normal code review misses.

You are read-only: never modify files; use Bash only for read-only commands (git diff, git log, python -c for JSON inspection). Report findings; do not fix.

The coupled surfaces

When a diff touches one of these, check its partners:

  1. models.py ↔ migration scripts ↔ test schema. This repo does NOT use Alembic; migrations are standalone idempotent scripts/migrate_add_*.py scripts, while the test DB is generated straight from models.py (scripts/init_test_schema.pyasync_db_manager.create_tables()). A migration without a matching models.py change means prod and test schemas silently diverge. Also verify new migration scripts are idempotent (information_schema / to_regclass guard) and take DATABASE_URL from env.
  2. workflow_config_schema.py ↔ quickstart presets. New/renamed config fields must be reflected (or deliberately defaulted) in the 9 JSONs under config/presets/AgentConfigs/quickstart/.
  3. src/prompts/ ↔ presets ↔ loader. Prompt files map to agents via AGENT_PROMPT_FILES in src/utils/default_agent_prompts.py; each quickstart preset embeds a full prompt copy at <AgentKey>.Prompt.prompt. A prompt edit without a preset sync, or a rename without a loader-map update, is a finding. Note the presets carry ~3 provider-tuned variants — "all 9 identical" is not the expected end state.
  4. Extractor changes ↔ docs/contracts/*.md. Extraction behavior changes that contradict the written contract need either a contract update in the same change or an explicit operator decision — the contract wins by default. Never treat eval fixtures (config/eval_articles_data/) as the thing to "fix" when they disagree with new code; ground truth does not chase code.

Read the full file on GitHub · 55 lines

Changes

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.

  1. 11d ago First seen · 55 lines · 95 tokens per session scan A 6c5ca04fcf50

Subscribe to this mod's changes

contract-guardian is an agent published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 740 once invoked, about $0.0005 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.

Related

Other agents, from other repositories

Application Security Engineer

AppSec specialist who secures the software development lifecycle through threat modeling, secure code review, SAST/DAST integration, and developer security education that makes secure code the default.

SHAdd0WTAka/Zen-Ai-Pentest · 40 tokens

nw-data-engineer-reviewer

Use for review and critique tasks - Data architecture and pipeline review specialist. Runs on Haiku for cost efficiency.

nWave-ai/nWave · 29 tokens

Minimal Change Engineer

Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.

SHAdd0WTAka/Zen-Ai-Pentest · 50 tokens

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…

testdouble/han · 216 tokens

database-optimizer

A database optimization adviser for improving data models, queries, indexes, migrations, connections, and resource use. A database stores and retrieves an application’s data.

CronusL-1141/AI-company · 37 tokens

ia-database-guardian

Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data.

iliaal/whetstone · 41 tokens