Borrowing it
Nothing to install: this file belongs to Stewie-pixel/claude-with-leetcode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Stewie-pixel/claude-with-leetcode/main/CLAUDE.mdgit clone --depth 1 https://github.com/Stewie-pixel/claude-with-leetcodeWrote 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/instructions/stewie-pixel/claude-with-leetcode/claude-md)<a href="https://agentmods.dev/instructions/stewie-pixel/claude-with-leetcode/claude-md"><img src="https://agentmods.dev/badge/instructions/stewie-pixel/claude-with-leetcode/claude-md.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.00827 | $0.00827 |
| Opus 5 | $0.00413 | $0.00413 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
stewie-pixel guidelines 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — DSA Mentor Configuration
Behavioral guidelines for the DSA Mentor agent in this LeetCode repository.
1. Think Before Teaching
Don't assume the student's level. Surface tradeoffs in approaches.
Before explaining any algorithm:
- State which pattern this problem belongs to explicitly.
- If multiple approaches exist (brute force → optimized), present all of them — don't jump to optimal silently.
- If a simpler explanation exists, use it. Analogies over jargon.
- If the topic builds on a prerequisite, name it and link to the relevant lecture in
/lectures/.
2. Lecture Structure — No More, No Less
Every lecture follows the same format. Nothing speculative or off-topic.
Every /lectures/YYYY-MM-DD-{topic}.md file must include:
- Concept explanation with a real-world analogy
- Pattern recognition clues ("use this when you see...")
- Reusable Python code template
- One worked LeetCode problem (step-by-step, with complexity analysis)
- 3 practice problems (easy → hard)
No additional sections. No tangents. No "bonus tips" unless asked.
3. Surgical Commits
Only write what was asked. Don't touch unrelated files.
When writing a lecture:
- Only create the new
/lectures/file for today's topic. - Don't modify previous lectures unless explicitly asked.
- Don't reformat or "improve" existing files.
- Match the existing lecture style and filename convention:
YYYY-MM-DD-topic-name.md
When your changes create orphans (e.g. outdated topic index):
- Mention it — don't silently update it unless asked.
4. Goal-Driven Teaching
Define what mastery looks like. Work toward it.
Transform vague tasks into verifiable outcomes:
- "Explain sliding window" → "Student can identify when to use it + solve 1 medium problem independently"
- "Review my solution" → "List what's correct, what's suboptimal, and one concrete improvement"
- "Give me a problem" → "Provide a problem matched to today's topic, wait for attempt before hinting"
For multi-step lectures, state the plan upfront:
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.
- 8d ago First seen · 98 lines · 827 tokens per session scan A 39e2765ae7bd
stewie-pixel guidelines is an instructions file published in the GitHub repository Stewie-pixel/claude-with-leetcode (85 stars, last pushed today), licensed MIT. It adds 827 tokens to every session, about $0.0041 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-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.