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/brycewang-stanford/stata-code/claude-mdgit clone --depth 1 https://github.com/brycewang-stanford/stata-codeWhat 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.01367 | $0.01367 |
| Opus 5 | $0.00683 | $0.00683 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
stata-code CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}\n" https://pypi.org/pypi/stata-code/X.Y.Z/json How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — stata-code project notes
Project-specific guidance for Claude Code sessions in this repo. General publishing docs live in PUBLISHING.md; this file captures what isn't obvious from reading the workflows.
Communication
Please think and talk with me in English.
Release coordination
A unified release ships four artifacts under the same version number:
| Channel | Tag | Workflow |
|---|---|---|
TestPyPI (stata-code) |
vX.Y.Z |
publish-testpypi job in .github/workflows/release.yml |
PyPI (stata-code) |
vX.Y.Z |
publish-pypi job in .github/workflows/release.yml |
VS Code Marketplace (stata-code-vscode) |
vscode-vX.Y.Z |
.github/workflows/vscode-release.yml |
| GitHub Release | vX.Y.Z |
tail end of release.yml |
Eight version literals (across six files) must move together, or the
release.yml "Verify tag matches project versions" gate (scripts/check_versions.py)
fails the build before any publish runs. Bump all of them, or run the guard
locally first (python3 scripts/check_versions.py --tag vX.Y.Z):
pyproject.toml→[project] versionstata_code/__init__.py→__version__stata_code/mcp/server.py→__version__vscode/package.json→versionvscode/package-lock.json→ top-levelversionandpackages[""].version(two sites).claude-plugin/plugin.json→version.claude-plugin/marketplace.json→metadata.versionand eachplugins[*].version(two sites)
vscode/src/mcpClient.ts imports the extension version from
vscode/package.json for the MCP handshake, so it should not carry a separate
literal.
PyPI / TestPyPI Trusted Publishing — what to know
Both PyPI and TestPyPI use OIDC (no API tokens in repo secrets). They are separate sites with separate publisher configs — each must be set up independently:
| Site | Manage URL | Environment |
|---|---|---|
| PyPI | https://pypi.org/manage/project/stata-code/settings/publishing/ | pypi |
| TestPyPI | https://test.pypi.org/manage/project/stata-code/settings/publishing/ | testpypi |
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 · 128 lines · 1,367 tokens per session scan A ba8d695e1dab
stata-code CLAUDE.md is an instructions file published in the GitHub repository brycewang-stanford/stata-code (41 stars, last pushed 23d ago), licensed MIT. It adds 1,367 tokens to every session, about $0.0068 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
streamlit copilot-instructions.md
Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
streamlit python_tests.instructions.md
Instructions for streamlit/streamlit, covering python unit test guide, key principles, running tests and typing tests.
streamlit agents.instructions.md
Instructions for streamlit/streamlit, covering agent definitions, file format, best practices, cross-platform compatibility and slash command support.
streamlit protobuf.instructions.md
Instructions for streamlit/streamlit, covering protobuf, compile protobuf and important files.
streamlit python_lib.instructions.md
Instructions for streamlit/streamlit, covering streamlit lib python guide, fips compatibility, logging, in-app ui vs console-only and metrics.
streamlit workflows.instructions.md
Instructions for streamlit/streamlit, covering github actions workflows, workflow guidelines, external actions policy, shell injection prevention and unsafe — value is injected directly into the shell command.