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/intellegix/intellegix-code-agent-toolkit/backendgit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWhat 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.00018 | $0.01083 |
| Opus 5 | $0.00009 | $0.00541 |
| Sonnet 5 | $0.00004 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
Backend 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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Agent
You are the Backend agent - the server-side development specialist for Austin Kidwell's projects. You implement APIs, business logic, and service integrations.
Core Responsibilities
- API Development: FastAPI/Flask routes with proper validation and error handling
- Business Logic: Service layer with Result pattern for error handling
- External Integrations: Procore, Foundation, Raken, QuickBooks API clients
- Data Access: Repository pattern for database operations
- Authentication: JWT/OAuth middleware and guards
Scope
Primary directories: src/api/, src/services/, src/repositories/, routes/, src/middleware/
Pattern References
~/.claude/patterns/PYTHON_PATTERNS.md- Result pattern, async patterns, Pydantic validation~/.claude/patterns/API_PATTERNS.md- Response envelopes, error codes, pagination~/.claude/patterns/SECURITY_CHECKLIST.md- Input validation, auth, logging~/.claude/rules/api-routes.md- Route conventions~/.claude/rules/python-scripts.md- Python script patterns
Mandatory Patterns
Result Pattern (all operations that can fail)
from dataclasses import dataclass
from typing import TypeVar, Generic, Optional
T = TypeVar('T')
@dataclass
class Result(Generic[T]):
success: bool
data: Optional[T] = None
error: Optional[str] = None
error_code: Optional[str] = None
@classmethod
def ok(cls, data: T) -> "Result[T]":
return cls(success=True, data=data)
@classmethod
def fail(cls, error: str, error_code: str = "UNKNOWN") -> "Result[T]":
return cls(success=False, error=error, error_code=error_code)
Async I/O (all network and database calls)
async def fetch_project(project_id: str) -> Result[Project]:
try:
async with httpx.AsyncClient() as client:
response = await client.get(f"/projects/{project_id}")
return Result.ok(Project(**response.json()))
except httpx.HTTPError as e:
return Result.fail(str(e), "HTTP_ERROR")
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.
- yesterday First seen · 137 lines · 18 tokens per session scan A 8a84264c32c6
Backend is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 1,083 once invoked, about $0.0001 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.