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/adamikhq/adamik-mcp-server/toolsarchitectureupdategit clone --depth 1 https://github.com/AdamikHQ/adamik-mcp-serverWrote 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/rules/adamikhq/adamik-mcp-server/toolsarchitectureupdate)<a href="https://agentmods.dev/rules/adamikhq/adamik-mcp-server/toolsarchitectureupdate"><img src="https://agentmods.dev/badge/rules/adamikhq/adamik-mcp-server/toolsarchitectureupdate.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.00000 | $0.01090 |
| Opus 5 | $0.00000 | $0.00545 |
| Sonnet 5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
toolsarchitectureupdate 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tools Architecture Documentation Update Rule
Trigger Conditions
This rule applies when:
src/module.tsis modified (tool additions, modifications, or deletions)- Any MCP server tool implementations are changed
- Tool descriptions or parameters are updated
Mandatory Actions Required
CRITICAL: Update TOOLS_ARCHITECTURE.md
When modifying src/module.ts, you MUST update TOOLS_ARCHITECTURE.md to maintain documentation synchronization.
Specific Update Requirements:
1. Tool Addition
If you add a new tool to src/module.ts:
- Categorize as Operational or Specification tool
- Add to appropriate section in TOOLS_ARCHITECTURE.md
- Update the
readMeFirsttool description if categories change - Add usage examples and common workflows
- Document any chain-specific behaviors
- Update the tool count in overview section
2. Tool Modification
If you modify an existing tool:
- Update tool description in TOOLS_ARCHITECTURE.md
- Modify affected usage patterns and examples
- Update workflow documentation if behavior changes
- Verify examples still reflect current API
- Update parameter documentation if inputs/outputs change
3. Tool Removal
If you remove a tool:
- Remove from TOOLS_ARCHITECTURE.md categories
- Update
readMeFirsttool if needed - Remove or update affected workflows
- Update examples that reference the removed tool
- Check for broken workflow dependencies
4. Parameter Changes
If you modify tool parameters:
- Update parameter descriptions in documentation
- Modify code examples to reflect new parameters
- Update validation rules documentation
- Verify chain-specific parameter guidance
Documentation Sections to Review:
- Tool Categories - Ensure new/modified tools are properly categorized
- LLM Usage Patterns - Update examples with current tool calls
- Common Workflows - Verify workflows still work with changes
- Best Practices - Add new guidance for new tools
- Chain Family Specifics - Document any chain-specific behaviors
- Example Scenarios - Update scenarios to reflect current capabilities
- Maintenance Guidelines - Keep checklists current
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 · 134 lines · 0 tokens per session scan A e8be4c428ec7
toolsarchitectureupdate is a cursor rule published in the GitHub repository AdamikHQ/adamik-mcp-server (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,090 tokens. 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.