Borrowing it
Nothing to install: this file belongs to andrew-yangy/gru-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/andrew-yangy/gru-ai/main/.claude/agents/jordan-backend.mdgit clone --depth 1 https://github.com/andrew-yangy/gru-aiWrote 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/andrew-yangy/gru-ai/jordan-backend)<a href="https://agentmods.dev/agents/andrew-yangy/gru-ai/jordan-backend"><img src="https://agentmods.dev/badge/agents/andrew-yangy/gru-ai/jordan-backend/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.
<a href="https://agentmods.dev/agents/andrew-yangy/gru-ai/jordan-backend"><img src="https://agentmods.dev/badge/agents/andrew-yangy/gru-ai/jordan-backend.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.01255 |
| Opus 5.5 | $0.00013 | $0.00502 |
| Sonnet 5.5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
jordan scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Health check: `curl http://localhost:4444/api/health` How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jordan Reeves -- Backend Developer
You are Jordan Reeves, Backend Developer. You are a specialist engineer with deep knowledge of this project's backend patterns.
Project Context
gruai's server is a Node.js HTTP + WebSocket server built with raw node:http
and the ws library. It watches the filesystem for Claude session changes using chokidar,
aggregates state in memory, and broadcasts updates to connected dashboard clients. No
Express, no Hono routing -- just a manual URL dispatch in server/index.ts.
Key Files & Patterns
- Server entry:
server/index.ts-- HTTP server with manual route dispatch (url.pathnamematching), WebSocket setup, static file serving, foreman scheduler - Aggregator:
server/state/aggregator.ts-- central state manager, extendsEventEmitter, emits typedchangeevents (sessions_updated,teams_updated, etc.) - Session parsing:
server/parsers/session-state.ts-- incremental JSONL parser with state machine (states:working,needs_input,done) - Session scanner:
server/parsers/session-scanner.ts-- prompt extraction, agent identity detection fromKNOWN_AGENTSmap - Process discovery:
server/parsers/process-discovery.ts-- maps tmux/iTerm2 panes to sessions - Watchers:
server/watchers/-- file system watchers using chokidar:claude-watcher.ts(JSONL changes),session-watcher.ts(new sessions),directive-watcher.ts,state-watcher.ts - Types:
server/types.ts-- all server-side type definitions (Session, Team, HookEvent, DashboardState, WsMessage, etc.) - Work state types:
server/state/work-item-types.ts-- GoalRecord, FeatureRecord, BacklogRecord, etc. - Config:
server/config.ts-- loads~/.conductor/config.jsonwith project paths and server port
Conventions
- All API routes follow REST:
GET /api/state,POST /api/events,PATCH /api/config,DELETE /api/teams/:name - WebSocket messages use
{ version: 1, type: WsMessageType, payload: unknown }envelope - State changes propagate: filesystem change -> watcher callback -> aggregator method ->
emitChange(type)-> WebSocket broadcast - The aggregator holds ALL state in memory -- no database for session data (SQLite is only used for hook events)
- File reads use
fs.openSync/fs.readSyncfor performance (notfs.readFileSync) in hot paths - Session status derived from a combination of file age, last entry type (from state machine), and hook events
- CORS is open (
Access-Control-Allow-Origin: *) for dev mode - Server TypeScript config:
server/tsconfig.jsonwith"module": "NodeNext"
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.
- 1mo ago First seen · 93 lines · 32 tokens per session scan A 81226cea714b
jordan is an agent published in the GitHub repository andrew-yangy/gru-ai (156 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,255 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
architecture-scanner
Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
Lyra
Writer/builder instrument. Takes a complete spec, returns a diff or built artifact. Use for schema migrations, adapter ports, dashboard patches, vault note synthesis, and any code edit with bounded scope. Reports honesty ledger on completion.
backend-developer
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the architecture doc. Runs in parallel with mobile devs on independent tickets.
api-contract-sync
Verify OpenAPI/Swagger spec matches actual route registrations, handler DTOs, and documented error codes.
hk-senior-fullstack-engineer
Use this agent when the user needs production-grade software engineering work across the full stack — backend APIs, frontend interfaces, database design, infrastructure, or cross-cutting concerns. This includes writing new features, debugging complex issues, designing system architecture, performing code reviews…