Borrowing it
Nothing to install: this file belongs to dubzdubz/ctx4-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/dubzdubz/ctx4-ai/main/AGENTS.mdgit clone --depth 1 https://github.com/dubzdubz/ctx4-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/instructions/dubzdubz/ctx4-ai/agents-md)<a href="https://agentmods.dev/instructions/dubzdubz/ctx4-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/dubzdubz/ctx4-ai/agents-md.svg" alt="Measured on agentmods" 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.01868 | $0.01868 |
| Opus 5 | $0.00934 | $0.00934 |
| Sonnet 5 | $0.00374 | $0.00374 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
ctx4-ai AGENTS.md 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 6d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctx4-ai - Agent Context
Next.js web app + MCP server for adding long-term context/memory to AI agents. Built with TypeScript, Next.js 16, and mcp-handler.
Quick Reference
- Stack: TypeScript, Next.js 16 (App Router), pnpm, mcp-handler, Vercel Sandbox, Supabase Auth, Drizzle ORM, GitHub App (Octokit), Storybook
- Dev server:
pnpm dev→ Next.js atlocalhost:3000, MCP atlocalhost:3000/mcp - Build:
pnpm build && pnpm start - Lint:
pnpm lint(Biome) /pnpm lint:fix - Storybook:
pnpm storybook→localhost:6006 - Test:
vitest(unit), Playwright (e2e via Storybook) - Auth: OAuth 2.0 via Supabase — standard OAuth flow with
/authorizeand/tokenendpoints
Project Structure
├── app/
│ ├── [transport]/route.ts # MCP handler (tools registration)
│ ├── api/
│ │ ├── github/ # GitHub App endpoints (callback, repos, select-repo, disconnect)
│ │ └── oauth/ # OAuth approval endpoint
│ ├── auth/ # OAuth endpoints
│ ├── settings/ # User settings / profile page (incl. GitHub integration)
│ ├── layout.tsx # Root layout
│ └── page.tsx # Home page
├── lib/
│ ├── auth/ # Auth utilities (verify-token)
│ ├── content/ # Built-in guide content
│ ├── db/ # Drizzle ORM (schema, queries, client)
│ ├── github/ # GitHub App client (Octokit, installation tokens)
│ ├── sandbox/ # SandboxManager, SandboxManagerPool, scanner
│ ├── supabase/ # Supabase client helpers
│ ├── tools/ # MCP tool implementations
│ └── utils.ts # Shared utilities
├── components/
│ ├── github/ # GitHub integration UI (repo manager)
│ ├── auth/ # Auth components
│ └── ui/ # Shadcn UI components
├── drizzle/ # Database migrations
├── scripts/ # Build/dev scripts
├── docs/ # Project documentation
│ ├── architecture.md # Architecture decisions
│ ├── product.md # Product overview
│ ├── style-guide.md # Code style & linting
│ └── ui-guide.md # UI components & design handling
└── CLAUDE.md # This file (always in context)
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.
- 6d ago First seen · 171 lines · 1,868 tokens per session scan A 778570697abe
ctx4-ai AGENTS.md is an instructions file published in the GitHub repository dubzdubz/ctx4-ai (1 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,868 tokens to every session, about $0.0093 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.