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/hollobit/assembly-api-mcp/claude-mdgit clone --depth 1 https://github.com/hollobit/assembly-api-mcpWrote 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/hollobit/assembly-api-mcp/claude-md)<a href="https://agentmods.dev/instructions/hollobit/assembly-api-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/hollobit/assembly-api-mcp/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.1 | $0.00692 | $0.00692 |
| Opus 5 | $0.00346 | $0.00346 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
assembly-api-mcp 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 6d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill routing
When the user's request matches an available skill, ALWAYS invoke it using the Skill tool as your FIRST action. Do NOT answer directly, do NOT use other tools first. The skill has specialized workflows that produce better results than ad-hoc answers.
Key routing rules:
- Product ideas, "is this worth building", brainstorming → invoke office-hours
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
- Ship, deploy, push, create PR → invoke ship
- QA, test the site, find bugs → invoke qa
- Code review, check my diff → invoke review
- Update docs after shipping → invoke document-release
- Weekly retro → invoke retro
- Design system, brand → invoke design-consultation
- Visual audit, design polish → invoke design-review
- Architecture review → invoke plan-eng-review
- Save progress, checkpoint, resume → invoke checkpoint
- Code quality, health check → invoke health
- MCP 도구 개선, API 통합, 도구 구조 분석 → invoke assembly-orchestrator
- API 커버율 분석 → invoke analyze-mcp
- 도구 코드 구현/수정 → invoke implement-mcp
Design files
- Visual/site/brand work must use
./design/DESIGN.mdas the source of truth. - External design references and generated design docs belong under
./design/, not./docs/or_workspace/. docs/mcp-design-analysis.mdis tool architecture analysis, not the canonical visual design file.
하네스: 국회 MCP 서버 개선
목표: assembly-api-mcp의 276개 API → MCP 도구 래핑 구조를 분석·최적화하고, 승인된 개선안을 구현한다
에이전트 팀:
| 에이전트 | 역할 | 파일 |
|---|---|---|
| api-analyst | 276개 API 구조 분석, 중복/연관 파악, 통합 기회 도출 | .claude/agents/api-analyst.md |
| tool-designer | MCP 도구 인터페이스 UX 분석, 토큰 효율 최적화, AI 클라이언트 관점 설계 | .claude/agents/tool-designer.md |
| mcp-developer | 승인된 개선안 TypeScript 구현, 테스트 작성 | .claude/agents/mcp-developer.md |
스킬:
| 스킬 | 용도 | 사용 에이전트 |
|---|---|---|
| analyze-mcp | API 구조 분석 + 도구 설계 제안 | api-analyst, tool-designer |
| implement-mcp | 도구 코드 구현/수정 | mcp-developer |
| assembly-orchestrator | 분석→설계→구현 전체 워크플로우 조율 | 전체 |
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.
- 6d ago First seen · 57 lines · 692 tokens per session scan A 2c186267fab9
assembly-api-mcp CLAUDE.md is an instructions file published in the GitHub repository hollobit/assembly-api-mcp (89 stars, last pushed 4mo ago), licensed MIT. It adds 692 tokens to every session, about $0.0035 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
scalar AGENTS.md
AGENTS.md instructions for scalar/scalar, covering agents.md - ai agent guide for scalar, project overview, prerequisites, first-time setup and commands.
api-gateway CLAUDE.md
Claude Code instructions for membrane/api-gateway, covering claude.md, git & commit policy, working principles, 1. think before coding and 2. simplicity first.
LAP CLAUDE.md
Claude Code instructions for Lap-Platform/LAP, covering lap - lean api platform, what this is, quick reference, install and run tests.
apifable AGENTS.md
AGENTS.md instructions for ycs77/apifable, covering agents.md, keep this file strict, constraints, commands and rules.
robinhood-cli-mcp-api AGENTS.md
AGENTS.md instructions for zaydiscold/robinhood-cli-mcp-api, covering agents.md — driving robinhood-cli from an agent, what this is and how it works (read this for context), 0. tl;dr for an agent, 1. auth (browser-free, self-healing) and 2. discover the accounts — never hardcode them.
unsurf AGENTS.md
Instructions for acoyfellow/unsurf, covering agents.md — unsurf, what this is, stack, architecture and directory.