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/basecamp/basecamp-cli/agents-mdgit clone --depth 1 https://github.com/basecamp/basecamp-cliWhat 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.01669 | $0.01669 |
| Opus 5 | $0.00834 | $0.00834 |
| Sonnet 5 | $0.00334 | $0.00334 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
basecamp-cli AGENTS.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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Basecamp CLI Development Context
Getting Started
See CONTRIBUTING.md for build setup, testing, and PR workflow.
The standard development loop in this repo: make changes, run bin/ci, fix
what it catches, repeat until green, then push. Treat bin/ci as your
inner-loop companion, not a final hurdle.
Repository Structure
basecamp-cli/
├── cmd/basecamp/ # Main entrypoint
├── internal/
│ ├── appctx/ # Application context
│ ├── auth/ # OAuth authentication
│ ├── cli/ # CLI framework
│ ├── commands/ # Command implementations
│ ├── completion/ # Shell completion
│ ├── config/ # Configuration management
│ ├── dateparse/ # Date parsing
│ ├── hostutil/ # Host utilities
│ ├── models/ # Data models
│ ├── names/ # Name resolution
│ ├── observability/ # Tracing and metrics
│ ├── output/ # Output formatting
│ ├── presenter/ # Output presentation
│ ├── resilience/ # Retry and backoff
│ ├── sdk/ # Basecamp SDK wrapper
│ ├── tui/ # Terminal UI
│ └── version/ # Version info
├── e2e/ # BATS integration tests
├── skills/ # Agent skills
├── hooks/ # Agent lifecycle hooks (both agents)
├── .claude-plugin/ # Claude Code integration
└── .codex-plugin/ # Codex plugin manifest
Basecamp API Reference
API documentation: https://github.com/basecamp/bc3-api
Key endpoints used by the CLI:
/projects.json- List projects/buckets/{id}/todolists/{id}/todos.json- Todos in a list/buckets/{id}/todos/{id}/completion.json- Complete todo/people.json- List people/my/profile.json- Current user
Search: Use basecamp search "query" for full-text search across projects. The Recordings API (basecamp recordings) is for browsing by type/status without a search term.
Testing
bin/ci is the local CI gate. It runs every check that remote CI runs:
formatting, vetting, linting, unit tests, e2e tests, naming conventions,
CLI surface snapshots, skill drift detection, SDK provenance, and go mod tidy.
Run it early and often — after finishing a feature, after fixing a bug, before
pushing. If you're about to git push and haven't run bin/ci in this
session, stop and run it first.
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.
- 2d ago First seen · 159 lines · 1,669 tokens per session scan A e75d0d8b9a51
basecamp-cli AGENTS.md is an instructions file published in the GitHub repository basecamp/basecamp-cli (259 stars, last pushed 2d ago), licensed MIT. It adds 1,669 tokens to every session, about $0.0083 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
Basecamp-MCP-Server CLAUDE.md
Instructions for georgeantonopoulos/Basecamp-MCP-Server, covering claude.md, development commands, setup (one-time) - requires python 3.10+, option 2: using pip (if python 3.10+ already installed) and oauth authentication.
shapeup-sdlc-plugin AGENTS.md
Instructions for nguyenvanphituoc/shapeup-sdlc-plugin, covering shape up sdlc local harness, enforcement model, phase 1 — shaping (/shapeup), phase 2 — betting (po governance, no skill) and phase 3 — building.
shapeup-sdlc-plugin CLAUDE.md
Instructions for nguyenvanphituoc/shapeup-sdlc-plugin, covering claude.md, what this repo is, commands, rules that prevent breakage and keeping the docs and the plugin honest.
skills AGENTS.md
AGENTS.md instructions for basecamp/skills, covering basecamp skills repo, key constraints and repo structure.
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.
buildNext
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).