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.
git clone --depth 1 https://github.com/DXHeroes/mcp-devtoolsWrote 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/dxheroes/mcp-devtools/repository-structure)<a href="https://agentmods.dev/rules/dxheroes/mcp-devtools/repository-structure"><img src="https://agentmods.dev/badge/rules/dxheroes/mcp-devtools/repository-structure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/dxheroes/mcp-devtools/repository-structure"><img src="https://agentmods.dev/badge/rules/dxheroes/mcp-devtools/repository-structure.svg" alt="Reviewed on agentmods" width="80" 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.00644 |
| Opus 5.5 | $0.00000 | $0.00258 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
repository-structure 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Structure Guidelines
The MCP DevTools repository follows a monorepo structure with clear organization of packages and shared resources.
@file package.json @file packages/jira/package.json @file .cursor/rules/core-libraries-usage.mdc
Top-Level Directory Structure
mcp-devtools/
├── .github/ # GitHub workflows and templates
├── .cursor/ # Cursor IDE configuration
│ └── rules/ # Project coding rules and guidelines
├── packages/ # Individual MCP packages
│ ├── core/ # Core shared libraries
│ ├── jira/ # Jira integration package
│ ├── github/ # GitHub integration package
│ └── ... # Other integration packages
├── examples/ # Example usage of MCP DevTools
├── scripts/ # Build and maintenance scripts
├── docs/ # Documentation files
├── package.json # Root package.json
└── README.md # Root README
Package Structure
Each package in the packages/ directory should follow this structure:
packages/[package-name]/
├── src/ # Source code
│ ├── index.ts # Package entry point
│ ├── tools/ # MCP tool implementations
│ │ ├── tool1.ts # Individual tool implementation
│ │ └── index.ts # Tools export file
│ ├── api/ # API client code
│ └── types/ # TypeScript type definitions
├── test/ # Test files
├── dist/ # Compiled output (not in git)
├── package.json # Package manifest
├── tsconfig.json # TypeScript configuration
└── README.md # Package documentation
Package Naming Conventions
- All packages should be named with the
@mcp-devtools/prefix - Package names should be simple and descriptive (e.g.,
@mcp-devtools/jira) - Use kebab-case for package names (e.g.,
@mcp-devtools/github-actions)
Dependency Management
- Core dependencies should be defined in the root
package.json - Package-specific dependencies should be in each package's
package.json - Use exact versions for dependencies to ensure consistency
- Use peerDependencies for framework dependencies
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.
- 1mo ago First seen · 85 lines · 644 tokens per session scan A 9bea36e95012
repository-structure is a cursor rule published in the GitHub repository DXHeroes/mcp-devtools (13 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 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-30.
Other cursor rules, from other repositories
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
rule
AI/ML Python development (PyTorch, scikit-learn).
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.