Borrowing it
Nothing to install: this file belongs to jentic/jentic-one. 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/jentic/jentic-one/main/CLAUDE.mdgit clone --depth 1 https://github.com/jentic/jentic-oneWrote 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/jentic/jentic-one/claude-md)<a href="https://agentmods.dev/instructions/jentic/jentic-one/claude-md"><img src="https://agentmods.dev/badge/instructions/jentic/jentic-one/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.1 | $0.03095 | $0.03095 |
| Opus 5 | $0.01548 | $0.01548 |
| Sonnet 5 | $0.00619 | $0.00619 |
| Haiku 4.5 | $0.00310 | $0.00310 |
Grade A, and why
jentic-one 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 7d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
If
.rules/exists, read.rules/AGENTS.mdand use it instead of this file. Otherwise use the guidance below.
Quick Start
make install # Full dev setup: sync deps + install lefthook hooks
make check # Run lint + typecheck + score + tests
Rules & Guides
Architectural conventions and patterns are enforced by the architecture tests
in tests/arch/ and the scoped rules under
.cursor/rules/. Consult those before making changes to:
- ORM models, migrations, or repositories
- Service-layer code
- Web/HTTP handlers
- Architecture tests
Commands
| Target | Description |
|---|---|
help |
Show available targets |
install |
Full dev setup: sync deps + install lefthook hooks |
sync |
Install/sync project + dev dependencies |
lock |
Refresh the lockfile |
upgrade |
Upgrade locked dependencies |
fmt |
Format code with ruff |
fix |
Auto-fix lint issues and reformat code |
lint |
Lint (ruff check + format check + mypy) |
typecheck |
Run mypy |
test |
Run unit tests |
test-unit |
Run unit tests |
test-fast |
Run unit + arch tests (no external services) |
test-integration |
Run integration tests (requires running fixtures) |
test-arch |
Run architecture enforcement tests |
test-smoke |
Run smoke tests (requires running services) |
cov |
Run tests with coverage report |
score |
Validate OpenAPI specs with scorecard (80+ req) |
check |
Run lint, score, secrets audit, unit + arch tests |
hooks |
Install lefthook git hooks (pre-commit + commit-msg) |
clean |
Remove caches and build artifacts |
start-fixtures |
Start Docker database fixtures |
stop-fixtures |
Stop Docker database fixtures |
destroy-fixtures |
Remove Docker database fixtures and volumes |
start-app |
Start combined app (all surfaces) |
start-registry |
Start registry surface standalone |
start-admin |
Start admin surface standalone |
start-control |
Start control surface standalone |
build-all |
Build every service Docker image (see deploy/README.md) |
save-all |
Write image tarballs to build/jentic-<svc>-<ver>.tar |
images |
List locally-built jentic-one/* images |
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.
- 7d ago First seen · 218 lines · 3,095 tokens per session scan A 6467cb24a1f3
jentic-one CLAUDE.md is an instructions file published in the GitHub repository jentic/jentic-one (175 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,095 tokens to every session, about $0.0155 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
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).
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.
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).
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.