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/chrishunt/sotalog/claude-mdgit clone --depth 1 https://github.com/chrishunt/SOTALogWrote 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/chrishunt/sotalog/claude-md)<a href="https://agentmods.dev/instructions/chrishunt/sotalog/claude-md"><img src="https://agentmods.dev/badge/instructions/chrishunt/sotalog/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.00880 | $0.00880 |
| Opus 5 | $0.00440 | $0.00440 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
SOTALog 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOTA Log Agent Guide
Read DESIGN.md first. It contains the app's design philosophy, architecture, data model, UI conventions, and interaction patterns. Understand the design before making any changes.
Repository Structure
This monorepo contains two independent native apps:
ios/— Swift/SwiftUI iOS app (iOS build & deploy instructions)android/— Kotlin/Jetpack Compose Android app (Android build & deploy instructions)
Shared documentation at the root (DESIGN.md, CHANGELOG.md, VERSION) keeps both platforms aligned. The apps share no compiled code — each is fully native and self-contained.
Version Management
The VERSION file at the repo root is the single source of truth for the app version (e.g. 1.3). Both platforms read from this file:
- iOS:
MARKETING_VERSIONinios/project.ymlmust matchVERSION - Android:
build.gradle.ktsreadsVERSIONforversionName
Build numbers are managed independently per platform.
Commit Standards
- Short subject lines following standard git conventions
- Never reference AI tools in commits, code, or anywhere in the codebase
Cross-Platform Feature Porting
When asked to port iOS changes to Android:
-
Read the iOS changes: Check
git logandgit diffinios/to understand what changed. Read the modified iOS source files completely. -
Identify the layers affected and map to Android locations:
iOS Layer iOS Location Android Location Translation Models ios/SOTALog/Models/android/.../domain/models/struct → data class Pure Services ios/SOTALog/Services/android/.../domain/services/static enum → object DB Repos ios/SOTALog/Services/Database/android/.../data/repositories/GRDB → Room DAO + Repository DB Migrations ios/SOTALog/App/AppDatabase.swiftandroid/.../data/local/database/migration/GRDB migration → Room Migration Network ios/SOTALog/Services/Network/android/.../data/remote/api/URLSession → Retrofit ViewModels ios/SOTALog/ViewModels/android/.../ui/<feature>/@Observable → ViewModel + StateFlow Views ios/SOTALog/Views/android/.../ui/<feature>/SwiftUI → @Composable Tests ios/SOTALogTests/android/app/src/test/XCTest → JUnit5 + MockK
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.
- 3d ago First seen · 67 lines · 880 tokens per session scan A 93cc1319e35d
SOTALog CLAUDE.md is an instructions file published in the GitHub repository chrishunt/SOTALog (2 stars, last pushed 1mo ago), licensed MIT. It adds 880 tokens to every session, about $0.0044 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
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.