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/PackmindHub/packmindWrote 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/packmindhub/packmind/standard-nestjs-module-hierarchy)<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-nestjs-module-hierarchy"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-nestjs-module-hierarchy/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/packmindhub/packmind/standard-nestjs-module-hierarchy"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-nestjs-module-hierarchy.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.00314 | $0.00314 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
standard-nestjs-module-hierarchy 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.
What it actually says
Standard: NestJS Module Hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... :
- Accept a single typed Command object as the input parameter in service methods instead of multiple individual parameters to enforce explicit intent and maintain consistency with the hexagonal architecture
- Configure all hierarchical routing exclusively in AppModule using RouterModule.register() with nested children arrays to ensure a single source of truth for the entire API route structure
- Create a dedicated NestJS module for each resource type, preventing controllers from handling sub-resource routes to maintain clear separation of concerns
- Define controller routes using empty @Controller() decorators to inherit path segments from RouterModule configuration and avoid path duplication
- Import child modules in parent module's imports array and register them as children in AppModule's RouterModule configuration to establish proper module dependencies
- Include all parent resource IDs in URL paths to make hierarchical relationships explicit and enable proper resource scoping and validation
- Place module files in directories that mirror the URL path hierarchy to make the codebase structure immediately understandable
- Use organization ID from route parameters (@Param('orgId')) instead of extracting it from AuthRequest to ensure consistency with the URL hierarchy
Full standard is available here for further request: NestJS Module Hierarchy
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 · 17 lines · 314 tokens per session scan A aab8e454a10d
standard-nestjs-module-hierarchy is a cursor rule published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 3d ago), licensed Apache-2.0. It adds 314 tokens to every session, about $0.0013 per session on Opus 5.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 cursor rules, from other repositories
cursorrules
Cursor rule "cursorrules" from googlarz/agents-sync, covering .cursorrules — managed by agents-sync v1.0.0, language: typescript / next.js 14 and run tests: npm test.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
conditionally-branching-workflows
Cursor rule "conditionally-branching-workflows" from PaulJPhilp/EffectPatterns, covering conditionally branching workflows and example.
create-a-service-layer-from-a-managed-resource
Cursor rule "create-a-service-layer-from-a-managed-resource" from PaulJPhilp/EffectPatterns, covering create a service layer from a managed resource and example.