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-back-end-typescript-clean-code-practices)<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-back-end-typescript-clean-code-practices"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-back-end-typescript-clean-code-practices/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-back-end-typescript-clean-code-practices"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-back-end-typescript-clean-code-practices.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.00252 | $0.00252 |
| Opus 5.5 | $0.00101 | $0.00101 |
| Sonnet 5.5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
standard-back-end-typescript-clean-code-practices 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 24d 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: Back-end TypeScript Clean Code Practices
This standard establishes clean code practices in TypeScript for back-end development to enhance maintainability and ensure consistent patterns across services. It covers logging best practices, error... :
- Avoid excessive logger.debug in production code; use logger.info for important business events and logger.error only for failures nothing else records, adding logger.debug while debugging.
- Extend the package's
DomainError,PackmindInternalErrororPackmindUpstreamErrorbase when defining an error class; only a family base itself extendsError. - Inject PackmindLogger as a constructor parameter with a default value using a variable or a string representing the class name.
- Instantiate use cases in adapters without passing the adapter's logger; use cases must create their own logger for proper origin tracking.
- Keep all import statements at the top of the file before any other code. Never use dynamic imports in the middle of the code unless absolutely necessary for code splitting or lazy loading.
Full standard is available here for further request: Back-end TypeScript Clean Code Practices
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.
- 24d ago Changed · -10 tokens per session 7dfbc9d8ec0b
- 25d ago Changed · +2 tokens per session 268c2c9c8523
- 1mo ago First seen · 14 lines · 260 tokens per session scan A e39cc14cf252
standard-back-end-typescript-clean-code-practices is a cursor rule published in the GitHub repository PackmindHub/packmind (319 stars, last pushed yesterday), licensed Apache-2.0. It adds 252 tokens to every session, about $0.0010 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.