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 skills add DojoCodingLabs/code-sensei --skill architecturegit clone --depth 1 https://github.com/DojoCodingLabs/code-senseiWrote 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/skills/dojocodinglabs/code-sensei/architecture)<a href="https://agentmods.dev/skills/dojocodinglabs/code-sensei/architecture"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/architecture/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/skills/dojocodinglabs/code-sensei/architecture"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/architecture.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.00026 | $0.00591 |
| Opus 5.5 | $0.00010 | $0.00236 |
| Sonnet 5.5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
architecture 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- architecture — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture — CodeSensei Teaching Module
What is Architecture?
- Analogy: Architecture is the floor plan of your application. Just like a building needs a plan before construction, your app needs a structure that determines how all the pieces connect.
- Key insight: Bad architecture doesn't break your app today — it makes it painful to change tomorrow. Good architecture makes change easy.
Client-Server Architecture
- The pattern: Frontend (client) ↔ API ↔ Backend (server) ↔ Database
- Why this split: Separation of concerns. The frontend handles display, the backend handles logic and data. They can change independently.
- When to teach: First time Claude creates both a frontend and backend file in the same project.
Monolith vs Microservices
- Monolith: Everything in one codebase. Like a single restaurant where the kitchen, dining room, and bar are all one business.
- Microservices: Each feature is its own mini-app. Like a food court where each stall is independent.
- Key insight for vibecoders: Start monolith. Always. Microservices are for when you have scaling problems, not before.
MVC Pattern
- Model — the data layer (what your app knows)
- View — the display layer (what the user sees)
- Controller — the logic layer (what happens when the user does something)
- Analogy: A restaurant. The menu (model) has the dishes. The table presentation (view) is what the customer sees. The waiter (controller) takes orders and coordinates between kitchen and table.
State Management
- The problem: As your app grows, keeping track of data that multiple components need becomes messy.
- Analogy: In a small office, everyone shouts across the room. In a big company, you need an organized messaging system (Slack, email).
- Solutions: React Context, Redux, Zustand — all solve the same problem differently.
Caching
- Analogy: Instead of cooking every meal from scratch, you prep common ingredients in advance. Caching stores frequently-used data closer to where it's needed so you don't have to fetch it every time.
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 · 46 lines · 26 tokens per session scan A 1f68150221ab
architecture is a skill published in the GitHub repository DojoCodingLabs/code-sensei (14 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 591 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-durable-objects
Cloudflare Durable Objects for stateful coordination and real-time apps. Use for chat, multiplayer games, WebSocket hibernation, or encountering class export, migration, alarm errors.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
cloudflare-workflows
Cloudflare Workflows for durable long-running execution. Use for multi-step workflows, retries, state persistence, or encountering NonRetryableError, execution failed errors.
cloudflare-email-routing
Cloudflare Email Routing for receiving/sending emails via Workers. Use for email workers, forwarding, allowlists, or encountering Email Trigger errors, worker call failures, SPF issues.