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/ryu0118/xcstrings-crud/claude-mdgit clone --depth 1 https://github.com/Ryu0118/xcstrings-crudWrote 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/ryu0118/xcstrings-crud/claude-md)<a href="https://agentmods.dev/instructions/ryu0118/xcstrings-crud/claude-md"><img src="https://agentmods.dev/badge/instructions/ryu0118/xcstrings-crud/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.00400 | $0.00400 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
xcstrings-crud 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.
What it actually says
xcstrings-crud
CLI and MCP server for xcstrings (String Catalog) CRUD operations.
Build & Test
swift build # Build all targets
swift test # Run all tests
swift build -c release # Release build
Architecture
XCStringsKit/- Core library (models, parser, reader, writer, stats)XCStringsCLI/- CLI commands using ArgumentParser (includes MCP subcommand)XCStringsMCP/- MCP server using swift-sdkxcstrings-crud/- CLI entry point (xcstrings-crud mcpfor MCP server)
Code Style
- Swift 6.0 with strict concurrency
- Use
async/awaitfor async operations - Errors defined in
Errors.swift, useXCStringsErrorenum - All public APIs should have clear parameter names
Key Files
XCStrings.swift- Data models (StringCatalog,StringUnit, Xcode metadata fields, etc.)XCStringsParser.swift- Facade for file operations, including multi-file untranslated checksXCStringsReader.swift- Read operations (list, get, check), including key metadata,shouldTranslate == falsehandling, and untranslated issue detection for specific files and languagesXCStringsWriter.swift- Write operations (add, update, delete, rename)XCStringsFileEncoder.swift- Deterministic xcstrings JSON encoding with Xcode-like key orderXCStringsKeySorter.swift- Xcode-like natural sorting for string catalog keysXCStringsStatsCalculator.swift- Coverage and progress stats; non-translatable keys are excluded from language totals
Testing
swift test --filter XCStringsKitTests # Run specific test target
Tests use fixture-based approach. See TestFixtures.swift for test data generation.
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 · 44 lines · 400 tokens per session scan A 95476d40d111
xcstrings-crud CLAUDE.md is an instructions file published in the GitHub repository Ryu0118/xcstrings-crud (23 stars, last pushed 4d ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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.