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/henriquemoody/charlieWrote 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/henriquemoody/charlie/dir.code-style)<a href="https://agentmods.dev/rules/henriquemoody/charlie/dir.code-style"><img src="https://agentmods.dev/badge/rules/henriquemoody/charlie/dir.code-style/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/henriquemoody/charlie/dir.code-style"><img src="https://agentmods.dev/badge/rules/henriquemoody/charlie/dir.code-style.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.00298 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
dir.code-style 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 2mo 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
Python Style
- Use Black for formatting (line length: 100)
- Use type hints for all function parameters and return types
- Follow PEP 8 conventions
- Use docstrings for all public functions and classes
Example:
def calculate_total(items: List[Item]) -> Decimal:
"""Calculate total price including tax.
Args:
items: List of items to calculate
Returns:
Total price with tax applied
"""
subtotal = sum(item.price for item in items)
return subtotal * Decimal("1.08")
TypeScript Style
- Use Prettier for formatting
- Enable strict mode in tsconfig.json
- Prefer const over let
- Use explicit types (avoid 'any')
- Use interfaces for object shapes
Example:
interface UserProfile {
id: string;
name: string;
email: string;
createdAt: Date;
}
const fetchUserProfile = async (userId: string): Promise<UserProfile> => {
const response = await api.get(`/users/${userId}`);
return response.data;
};
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.
- 2mo ago First seen · 55 lines · 0 tokens per session scan A da12afbf1df7
dir.code-style is a cursor rule published in the GitHub repository henriquemoody/charlie (7 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 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
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
naming-cheatsheet
Naming things is hard. This cheatsheet makes it easier. The codebase is primarily Python, so all examples use Python / PEP 8 conventions unless noted otherwise.
typescript
on how to run them.