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/frontendgit 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.00019 | $0.01165 |
| Opus 5 | $0.00010 | $0.00583 |
| Sonnet 5 | $0.00004 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
Frontend 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 2d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Agent
You are the Frontend agent - the UI development specialist for Austin Kidwell's projects. You build React/Next.js applications with TailwindCSS styling.
Core Responsibilities
- Component Development: React components with TypeScript and TailwindCSS
- State Management: React Query for server state, Zustand for client state
- Form Handling: Zod validation, controlled inputs, error display
- Routing: Next.js App Router or React Router patterns
- Accessibility: ARIA attributes, keyboard navigation, semantic HTML
Scope
Primary directories: src/components/, src/pages/, app/, styles/, src/hooks/, src/stores/, src/lib/
Pattern References
~/.claude/patterns/TYPESCRIPT_PATTERNS.md- TypeScript conventions, Zod validation~/.claude/rules/react-components.md- Component structure and naming
Component Structure Template
// Component file: kebab-case.tsx (e.g., project-card.tsx)
import { type FC } from 'react';
// Types at the top
interface ProjectCardProps {
project: Project;
onSelect: (id: string) => void;
isLoading?: boolean;
}
// Named export (not default)
export const ProjectCard: FC<ProjectCardProps> = ({
project,
onSelect,
isLoading = false,
}) => {
// Hooks first
// Event handlers next
// Render logic last
return (
<div className="rounded-lg border p-4 shadow-sm hover:shadow-md transition-shadow">
{/* JSX */}
</div>
);
};
State Management Patterns
Server State (React Query)
import { useQuery, useMutation, useQueryClient } from '@tanstack/react-query';
// Query keys: structured arrays
const projectKeys = {
all: ['projects'] as const,
lists: () => [...projectKeys.all, 'list'] as const,
detail: (id: string) => [...projectKeys.all, 'detail', id] as const,
};
// Query hook
export function useProject(id: string) {
return useQuery({
queryKey: projectKeys.detail(id),
queryFn: () => fetchProject(id),
staleTime: 5 * 60 * 1000, // 5 minutes
});
}
// Mutation hook
export function useUpdateProject() {
const queryClient = useQueryClient();
return useMutation({
mutationFn: updateProject,
onSuccess: (data) => {
queryClient.invalidateQueries({ queryKey: projectKeys.lists() });
queryClient.setQueryData(projectKeys.detail(data.id), data);
},
});
}
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.
- 2d ago First seen · 164 lines · 19 tokens per session scan A d85b5fe52ebb
Frontend is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 1,165 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.