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 instructions/eticmedya/uces/claude-mdgit clone --depth 1 https://github.com/eticmedya/ucesWrote 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/eticmedya/uces/claude-md)<a href="https://agentmods.dev/instructions/eticmedya/uces/claude-md"><img src="https://agentmods.dev/badge/instructions/eticmedya/uces/claude-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 | $0.00990 | $0.00990 |
| Opus 5 | $0.00495 | $0.00495 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
uces CLAUDE.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 4d 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.
UCES Core Directives
Reference: ~/.claude/CONVENTIONS.md for detailed standards
Intelligent Routing
Route requests to the appropriate skill module:
| Keywords | Module |
|---|---|
| component, page, UI, form, button, modal, React, Next.js, Tailwind, styling | ui |
| API, endpoint, route, database, REST, GraphQL, webhook, server, Supabase | api |
| mobile, Expo, React Native, NativeWind, iOS, Android, app | native |
| bug, error, fix, debug, broken, failing, test, spec | debug |
| auth, login, security, permission, OWASP, encryption, JWT | guard |
| plan, design, architecture, PRD, spec, requirements, system | architect |
| analytics, metrics, query, data, dashboard, report, KPI | data |
| deploy, CI/CD, Docker, pipeline, infrastructure, DevOps | devops |
Zero-Tolerance Enforcement
Blocked Patterns
- Placeholder data → Connect real sources
- Deferred implementations → Complete now
- Stub handlers → Full logic required
- Partial state handling → All states mandatory
- Loose typing → Strict TypeScript
- Silent failures → User feedback required
Completion Criteria
[✓] Integrated with actual data sources
[✓] States covered: loading, error, empty, success
[✓] Errors surface to user appropriately
[✓] TypeScript: zero errors
[✓] Production-ready quality
Verification Protocol
Before marking complete:
-
Execute validation:
npx tsc --noEmit # Must pass npm test # Must pass -
UI deliverables: Describe rendered state
-
API deliverables: Show response structure
-
Uncertainty: Explicitly state unknowns
Communication standards:
- Never claim unverified success
- Surface all warnings/errors
- Ask rather than assume
Implementation Templates
API Endpoint
// 1. Authentication
const session = await getSession()
if (!session) return unauthorized()
// 2. Input validation
const validated = Schema.safeParse(input)
if (!validated.success) return badRequest(validated.error)
// 3. Authorization
if (resource.ownerId !== session.userId) return forbidden()
// 4. Execution with error handling
try {
const result = await execute(validated.data)
return success(result)
} catch (e) {
log.error(e)
return serverError()
}
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.
- 4d ago First seen · 171 lines · 990 tokens per session scan A b4c1575cf405
uces CLAUDE.md is an instructions file published in the GitHub repository eticmedya/uces (106 stars, last pushed 7mo ago), licensed MIT. It adds 990 tokens to every session, about $0.0049 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-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.