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/cinqueizumi/softcover/claude-mdgit clone --depth 1 https://github.com/CinqueIzumi/SoftcoverWrote 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/cinqueizumi/softcover/claude-md)<a href="https://agentmods.dev/instructions/cinqueizumi/softcover/claude-md"><img src="https://agentmods.dev/badge/instructions/cinqueizumi/softcover/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.04500 | $0.04500 |
| Opus 5 | $0.02250 | $0.02250 |
| Sonnet 5 | $0.00900 | $0.00900 |
| Haiku 4.5 | $0.00450 | $0.00450 |
Grade A, and why
Softcover 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 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 — 140 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.
Project Overview
Softcover is a Kotlin Multiplatform / Compose Multiplatform client for Hardcover.app, a book tracking platform. It ships on Android (SDK 26+), iOS, and desktop (JVM), with shared UI and logic in commonMain and thin platform seams.
Engineering principles
Never take shortcuts; never propose the "less clean" option. When two solutions are available — a structurally clean one and a smaller-diff pragmatic one — pick the clean one and present it as the recommendation. Do not surface "less clean / pragmatic / repository-aggregator / pass-through delegation / cross-feature data-source reach" alternatives as primary recommendations. Mention a smaller-diff fallback only when the user explicitly asks for the cheaper path or when the clean option is genuinely out of scope. Cost (larger diff, more files touched, follow-up moves) is not a reason to defer; surface the cost transparently and proceed with the right structure unless told otherwise.
Build & Test Commands
./gradlew assembleDebug # Debug build
./gradlew assembleRelease # Release build
./gradlew test # Run unit tests
./gradlew :app:test # Run unit tests for app module
./gradlew connectedAndroidTest # Run instrumented tests (requires device/emulator)
./gradlew lint # Run Android Lint
The project uses kotlin.code.style=official. Both the foundation ktlint ruleset and detekt are
configured and gated (see Code Style below); ./gradlew styleCheck runs detekt + the mechanical checks,
and ./gradlew check runs the full set.
Design System
The brand-agnostic design skeleton (theme/typography plumbing, layout primitives, the shared component catalog, the editorial role contract) is governed by the foundation docs/rhaydus/0.3.1/design-system-foundations.md. docs/reference/design-system.md is the source of truth for Softcover's brand layered on top — color roles, editorial typography values, brand components, patterns, decision rules. It is split into section files under design-system/ behind a thin index; read only the section you need rather than the whole doc. Consult both before designing or modifying any UI surface.
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 · 140 lines · 4,500 tokens per session scan A e638a81b3838
Softcover CLAUDE.md is an instructions file published in the GitHub repository CinqueIzumi/Softcover (11 stars, last pushed 5d ago), licensed MIT. It adds 4,500 tokens to every session, about $0.0225 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).
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 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.
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.