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/embabel/embabel-agent/claude-mdgit clone --depth 1 https://github.com/embabel/embabel-agentWhat 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.00504 | $0.00504 |
| Opus 5 | $0.00252 | $0.00252 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
embabel-agent 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 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Important
- ALL instructions within this document MUST BE FOLLOWED, these are not optional unless explicitly stated.
- ASK FOR CLARIFICATION If you are uncertain of anything within the document.
- DO NOT edit more code than you have to.
- DO NOT WASTE TOKENS, be succinct and concise.
Coding Style
IMPORTANT: Adhere to coding style in .embabel/coding-style.md for coding style guidance.
Working Approach
NEVER execute git commit or push. You may use git tools for history, diffing or staging only.
ALWAYS work test first. When making an enhancement or fixing a bug, write failing tests first, then implement the feature or fix the bug to make the tests pass.
IMPORTANT: You should build the most relevant project (closest pom.xml) with Maven before presenting finished changes. Run the individual tests you have changed or that are most relevant.
If any change impacts usage of the project, update relevant documentation files.
Advice for Documentation in embabel-agent-docs
When working on documentation in the embabel-agent-docs module, follow these guidelines:
Use Asciidoctor syntax for writing documentation.
When asked to edit a particular .adoc file, look for a parallel file with a name prefixed with a . for instructions.
For example, if you are asked to edit tools.adoc, look for .tools.adoc for specific instructions about how to go
about it.
Thus you will be given a combination of user instructions such as ("edit tools.adoc to cover the FooBar tool in
FooBar.kt").
You will follow the user instruction but bear in mind the instructions in any .tools.adoc file.
If there is no ..adoc file, follow the general instructions in this document.
When writing documentation, ensure that you cover the following general instructions:
NEVER make up code unless asked. Code examples must come from the following repositories:
- This repository
- The
embabel-agent-examplesrepository at https://github.com/embabel/embabel-agent-examples/ - The
java-agent-templaterepository at https://github.com/embabel/java-agent-template/ - The
imprompturepository at https://github.com/embabel/impromptu/ - Any repositories the user specifically asks you to use
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 · 56 lines · 504 tokens per session scan A 0634cd7a776a
embabel-agent CLAUDE.md is an instructions file published in the GitHub repository embabel/embabel-agent (4,407 stars, last pushed yesterday), licensed Apache-2.0. It adds 504 tokens to every session, about $0.0025 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
spring-plugin AGENTS.md
Instructions for explyt/spring-plugin, covering agents.md — contributor guide, project structure, build, test, run, code style and conventions and commits and pull requests.
AgentStack convex.instructions.md
Instructions for ssdeanx/AgentStack, covering convex guidelines, function guidelines, new function syntax, http endpoint syntax and validators.
Next.js Best Practices
This rule provides comprehensive guidance for Next.js development, covering code organization, performance, security, testing, and common pitfalls. It helps developers build robust, scalable, and maintainable Next.js applications by adhering to community-accepted best practices and coding standards.
AgentStack update-docs-on-code-change.instructions.md
Automatically update README.md and documentation files when application code changes require documentation updates.
AgentStack agent-skills.instructions.md
Guidelines for creating high-quality Agent Skills for GitHub Copilot.
AgentStack code-review-generic.instructions.md
Generic code review instructions that can be customized for any project using GitHub Copilot.