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/icoretech/airbroke/project-structuregit clone --depth 1 https://github.com/icoretech/airbrokeWhat 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.00000 | $0.00426 |
| Opus 5 | $0.00000 | $0.00213 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
project-structure 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.
What it actually says
Project Structure
Overview
Airbroke uses the Next.js App Router. Most feature code lives under app,
components, lib, prisma, and __tests__.
Layout
app/: route segments, pages, layouts, and route handlers underapp/apicomponents/: shared presentation and feature UIcomponents/ui/: shadcn-style primitives consumed by the rest of the applib/: server helpers, auth, database access, cache helpers, queries, and server actionsprisma/: schema, migrations, seed script, and generated client output__tests__/: mirrors app, components, and lib with factories and helpers
Rules
- Keep route-local UI in the route segment when it is only used there.
Move reusable pieces into
components/orlib/. - Keep server actions in
lib/actions/*with"use server"at the top and keep their revalidation logic near the mutation. - Reuse the shared Prisma entrypoint in
lib/db.ts. Do not construct ad hoc Prisma clients in route handlers or components. - Use the
@/path alias instead of long relative imports. - Treat
lib/queries/*as the default read-path for database-backed UI. Keep mutations in server actions or dedicated server helpers. components/ui/**is excluded from the TypeScript project and bothcomponents/ui/**andcomponents/ai-elements/**are skipped by Biome. If you edit either area, keep the change narrow and manually verify the consuming screens.
Example Paths
app/projects/[project_id]: project-centric pages and filtersapp/api/mcp: MCP JSON-RPC entrypointlib/auth.ts: Better Auth configuration and provider restrictionslib/actions/projectActions.ts: server actions with revalidation and redirect flow__tests__/lib/projectActions.test.ts: server-action contract coverage
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 · 42 lines · 0 tokens per session scan A b15acfa088ac
project-structure is an agent published in the GitHub repository icoretech/airbroke (222 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 426 tokens. 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
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
software-engineer
Implements Accepted specs end to end, fixes bugs, and refactors without changing behaviour. Use proactively for new features once the spec is Accepted, domain/Prisma/Server Action changes, and technical approach decisions. Do not use when the request is a problem without a spec — that is product-manager.
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
domain-architect
Designs domain rules, invariants and pure function contracts before implementation. Use proactively for new features with non-trivial rules, ambiguous or conflicting requirements, calculations and state machines, inconsistencies between a spec and the code, or when deciding what belongs in domain versus services.