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 rules/burugo/one-mcp/tddgit clone --depth 1 https://github.com/burugo/one-mcpWhat 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.00000 | $0.01929 |
| Opus 5 | $0.00000 | $0.00964 |
| Sonnet 5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
tdd 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- API status endpoint: `curl "http://localhost:3003/api/status"` Copies of this mod
1 near-identical copy found in the catalogue:
- tdd — 88% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Final Verification:
Always use: go test -v ./backend/api/handler/... | grep FAIL
Debugging & Handling Verbose Output:
Avoid go test -v ./... directly in the terminal due to excessive output.
Recommended Alternatives:
- Specific Tests:
go test -v ./... -run ^TestSpecificFunction$(Fastest for pinpointing).
Project Startup and Logging Rules
Service Startup:
- Use
bash ./run.shto start the one-mcp service - This script automatically loads .env, ensures PATH, kills port 3000 processes, and starts the Go backend in background
- Logs are output to
backend.log
Log Monitoring:
- Use
tail -f backend.logto monitor real-time logs - Use
tail -n 50 backend.logto view recent log entries - Use
grep "ERROR\|WARN\|Failed" backend.logto filter error messages Service Management: - Use
pkill -f one-mcpto stop the service - Check service status with
ps aux | grep one-mcp | grep -v grep - API status endpoint:
curl "http://localhost:3003/api/status"
数据库重置和缓存管理
数据库重置规则:
- 重要: 删除数据库前必须先备份:
cp data/one-mcp.db data/one-mcp.db.backup.$(date +%Y%m%d_%H%M%S) - 仅删除数据库文件
rm -f data/one-mcp.db是不够的 - 必须同时清理Redis缓存:
redis-cli flushdb或redis-cli flushall - 原因:用户列表查询有缓存机制,如果缓存中存在用户数据,系统不会创建新的root用户
完整的数据库重置流程:
# 1. 停止服务
pkill -f one-mcp
# 2. 备份现有数据库
cp data/one-mcp.db data/one-mcp.db.backup.$(date +%Y%m%d_%H%M%S)
# 3. 删除数据库文件
rm -f data/one-mcp.db
# 4. 清理Redis缓存
redis-cli flushdb
# 5. 重新启动服务
bash ./run.sh
验证root用户创建:
- 查看日志:
grep "no user exists\|create a root user" backend.log - 检查数据库:
sqlite3 data/one-mcp.db "SELECT id, username, LENGTH(token) as token_length FROM users;"
前端API调用规范
API路径构建:
- 当使用
frontend/src/utils/api.ts中导出的api实例进行API调用时 (例如api.get,api.post等),请勿在请求路径中再次添加/api前缀。 - 这是因为
api实例的baseURL已经被配置为/api,重复添加会导致/api/api/这样的错误路径。 - 正确示例:
api.get('/user/self')或api.post('/user', data)。 - 错误示例:
api.get('/api/user/self')。
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 · 131 lines · 1,929 tokens per session scan A cc34a1ca0235
tdd is a cursor rule published in the GitHub repository burugo/one-mcp (412 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,929 tokens. 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 cursor rules, from other repositories
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI and config schema sync before lint, final checks.
mcp-debugging
Run the development restart script to rebuild and restart the muster service with your changes.
cmd-build
Implement the next task incrementally — build, test, verify, commit.
elite-developer
Principal Full-Stack Engineer for surgical implementation, strict TDD, complex debugging, and UI construction. Enforces the Agentic Company pipeline and high-rigor engineering standards. This agent contains the full knowledge of TDD, Systematic Debugging, Build Error Resolution, and Refactoring.
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.