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/sleuth-io/sx/claude-mdgit clone --depth 1 https://github.com/sleuth-io/sxWrote 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/sleuth-io/sx/claude-md)<a href="https://agentmods.dev/instructions/sleuth-io/sx/claude-md"><img src="https://agentmods.dev/badge/instructions/sleuth-io/sx/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.00736 | $0.00736 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
sx 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sx - Coding Agent Guide
Your team's private npm for AI assets - skills, MCP configs, commands, and more.
Quick Commands
make build # Build binary to ./dist/sx
make test # Run tests
make format # Format code
make lint # Run linter
make prepush # Format + lint + test + build (run before claiming done)
Before Reporting Work Complete
ALWAYS run make prepush before claiming a task is finished. CI runs
format, lint, tests, and build — if any of those fail locally, don't
tell the user the work is done.
Testing Local Changes
After making code changes, build and test with:
make build && ./dist/sx <command>
Tech Stack
- Go 1.25+
- cobra (CLI framework)
- TOML (config format)
Key Specifications
- Vault Spec - Vault structure and management
- Manifest Spec - sx.toml format (source of truth)
- Lock Spec - Per-user resolved lock file format
- Scoping - Overview of every install scope (org/repo/path/team/user/bot), links to per-scope docs
- Permissions / RBAC - github vault: who can set scope (org-admins) and who can edit a skill (team-scope membership)
- Vault copy -
sx vault copycross-vault migration (assets, teams, bots, scopes, audit, usage) - Synced folders - Shared path vaults inside Dropbox/Drive/OneDrive/iCloud folders
- Plugins - Exposing vaults as Claude Code / Codex plugin marketplaces
- Orgs - Org-scoped (global) installs
- Repos - Repo and path-scoped installs (monorepo patterns)
- Teams - Team management and team-scoped installs
- Users - Single-user installs and self-only restriction
- Bots - Bot identities and bot-scoped installs
- Audit log - Mutation audit trail format and queries
- Usage analytics -
sx statsdashboard and event format - Metadata Spec - Asset metadata format and fields
- MCP Spec - MCP server tools (query)
- Environment Variables - SX_CONFIG_DIR, SX_CACHE_DIR, and isolation recipes
- GitHub Actions - Installing from a private vault in CI (deploy keys, SX_SSH_KEY, SX_BOT)
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.
- today Changed · +1 lines · +32 tokens per session 83b79d0e79b3
- 4d ago First seen · 74 lines · 704 tokens per session scan A 9c45af5d47b1
sx CLAUDE.md is an instructions file published in the GitHub repository sleuth-io/sx (301 stars, last pushed today), licensed Apache-2.0. It adds 736 tokens to every session, about $0.0037 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.