Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/davidmatousek/tachinpx agentmods add rules/davidmatousek/tachi/info-disclosureWrote 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/davidmatousek/tachi/info-disclosure)<a href="https://agentmods.dev/rules/davidmatousek/tachi/info-disclosure"><img src="https://agentmods.dev/badge/rules/davidmatousek/tachi/info-disclosure.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.00046 | $0.01571 |
| Opus 5 | $0.00023 | $0.00785 |
| Sonnet 5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
info-disclosure 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata
category: stride
threat_class: I
dfd_targets: [Process, Data Store, Data Flow]
owasp_references:
- "OWASP Top 10 2021 A01:2021 — Broken Access Control"
- "OWASP Top 10 2021 A02:2021 — Cryptographic Failures"
- "OWASP API Security 2023 API3 — Broken Object Property Level Authorization"
- "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor"
- "CWE-209: Generation of Error Message Containing Sensitive Information"
- "CWE-532: Insertion of Sensitive Information into Log File"
- "MITRE ATT&CK T1005: Data from Local System"
output_schema: ../../../schemas/finding.yaml
Information Disclosure Threat Agent
Purpose
Detects threats where sensitive information is exposed to unauthorized parties — whether through direct data leaks, verbose error messages, side-channel observations, or insufficient access controls on stored data. Information disclosure violates confidentiality guarantees and can enable secondary attacks (credential harvesting, privilege escalation, social engineering). This agent targets Processes (where logic errors or misconfigurations expose internal state), Data Stores (where insufficient access controls expose persisted data), and Data Flows (where data in transit is observable by unauthorized parties).
Detection Scope
Targeted DFD Element Types
- Process: API endpoints, error handlers, search services, reporting engines, debug interfaces, health check endpoints
- Data Store: Databases, file storage, caches, session stores, backup systems, log aggregators
- Data Flow: API responses, inter-service messages, file transfers, email notifications, webhook payloads
Patterns and Indicators
Error Message Exposure
- Stack traces returned in API error responses (production environments)
- Database error messages revealing table names, column names, or query structure
- Framework version information in error pages or server headers
- File path disclosure in error messages exposing server directory structure
- Detailed validation errors revealing business rule internals
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.
- 4d ago First seen · 125 lines · 46 tokens per session scan A 8aba6a14e545
info-disclosure is a cursor rule published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 25d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,571 once invoked, about $0.0002 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-09-03.
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.