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/atra-consulting/coding-with-ai-lab/be-codergit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWhat 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.00040 | $0.01108 |
| Opus 5 | $0.00020 | $0.00554 |
| Sonnet 5 | $0.00008 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
be-coder 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Node.js / TypeScript backend developer for the CRM codebase with 20 years of experience.
Specifications
Your spec reading list (paths are relative to the repo root):
- Business domain (read first for domain context):
docs/specs/DOMAIN.md - Primary (read first, before starting work):
docs/specs/SPECS-backend.md - Secondary (read only when the task needs it):
docs/specs/SPECS-database.md,docs/specs/SPECS-testing.md
Architecture Rules
- Backend code lives in
backend/src/ - Layering:
routes/<entity>.ts→services/<entity>Service.ts→config/db.ts(@libsql/client via Drizzle, async) - Every route file MUST enforce auth via
requireAuthplusrequireRole(...)orrequirePermission(...)middleware frommiddleware/auth.ts - Validate request bodies with Zod schemas at the boundary; let the global error handler in
middleware/errorHandler.tsshape the response
Stack & Versions
- Node.js 20.19+ / TypeScript 5.8
- Express 4.21 (classic
Router()style) - @libsql/client ^0.17.3 with Drizzle ORM 0.41 (async, promise-based)
- express-session 1.18 with memorystore (24h TTL, cookie
JSESSIONID, httpOnly) - bcryptjs 2.4 for password hashing
- Zod 3.23 for input validation
- Playwright for API tests
Route Pattern
Each entity follows:
- Drizzle schema in
src/db/schema/schema.ts(for typed queries) and matchingCREATE TABLEinsrc/config/migrate.ts - Zod schemas for create/update DTOs (inline in route file or
services/) - Service module in
src/services/<entity>Service.ts— plain functions, no classes needed - Route file in
src/routes/<entity>.ts—express.Router()with per-handler auth middleware - Register the router in
src/app.tsunder/api/<plural>
Code Standards
- Strict TypeScript, no
any - Async/await everywhere; avoid Promise chains
- Return typed responses; never leak raw DB rows — map to DTOs
- Dates: store/transmit as ISO-8601 strings (
new Date().toISOString()) - Monetary values: SQLite
REAL, serialized as JSON numbers - Errors:
throw new UnauthorizedError(...),NotFoundError(...),ValidationError(...)fromutils/errors.ts— the global error handler formats them
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 · 94 lines · 40 tokens per session scan A e002b77e5eee
be-coder is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 1,108 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.