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.
npx agentmods add rules/ai-learning-gems/ai-learning-gems.github.io/high-quality-blogsgit clone --depth 1 https://github.com/AI-Learning-Gems/AI-Learning-Gems.github.ioWrote 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/ai-learning-gems/ai-learning-gems.github.io/high-quality-blogs)<a href="https://agentmods.dev/rules/ai-learning-gems/ai-learning-gems.github.io/high-quality-blogs"><img src="https://agentmods.dev/badge/rules/ai-learning-gems/ai-learning-gems.github.io/high-quality-blogs.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 | $0.00000 | $0.06862 |
| Opus 5 | $0.00000 | $0.03431 |
| Sonnet 5 | $0.00000 | $0.01372 |
| Haiku 4.5 | $0.00000 | $0.00686 |
Grade A, and why
high-quality-blogs 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 5d 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
High-Quality Technical Blogs & Sources
This is a curated registry of blogs and websites that produce textbook-quality technical content. When running the /research-textbook-chapter or /write-textbook-chapter workflows, the agent SHOULD search these sources for relevant material on the topic being researched.
How to Use This Registry
Attribution (MANDATORY)
These blogs contain original content by independent researchers and writers. When using their material in textbook chapters, you MUST:
- Cite the author and post in the section's collapsible source header table
- Attribute figures and diagrams in image captions:
Source: [Author Name], "[Post Title]" ([year]). [URL] - Quote, don't paraphrase — when using a specific explanation or framing from a blog post, use a blockquote with attribution rather than rewording it without credit
- Never present blog content as original — if an explanation or worked example is inspired by or adapted from a blog post, say so explicitly (e.g., "The following derivation is adapted from Gundersen's excellent treatment in [post title]")
During Research (MANDATORY)
When researching a topic, spend at least 2-3 searches specifically targeting these blogs:
site:lilianweng.github.io {TOPIC}
site:colah.github.io {TOPIC}
site:cameronrwolfe.substack.com {TOPIC}
site:magazine.sebastianraschka.com {TOPIC}
site:distill.pub {TOPIC}
site:gregorygundersen.com {TOPIC}
Pick the blogs most relevant to the topic's domain (see the category tags below).
During Source Downloading
Use the extraction method listed for each site. The authenticated_extract.py script handles most sites. Key notes:
- Substack sites auto-detect the
articleCSS selector - GitHub Pages blogs usually work with default settings (no
-sneeded) - Some sites need custom CSS selectors — see the "Extraction" field for each entry
Adding New Blogs to This Registry
When you discover a blog of exceptional quality during research, add it to this file following the template at the bottom. You MUST:
- Read at least 3 posts from the blog to assess quality and depth
- Test extraction with
authenticated_extract.pyto determine the best CSS selector - Categorize the blog using the depth tags defined below
- List 2-3 notable posts with URLs
- Add the entry in the correct category section
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.
- 5d ago First seen · 536 lines · 0 tokens per session scan A 4998f06373c1
high-quality-blogs is a cursor rule published in the GitHub repository AI-Learning-Gems/AI-Learning-Gems.github.io (22 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,862 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-30.
Other cursor rules, from other repositories
logseq-youtube-notes
Logseq-Flavored Markdown (LFM) YouTube transcript headings.
006_Program_of_Thought_Tutorial
DSPY 3 Program of Thought Tutorial - Production code reasoning system from official DSPy 3.0.1 tutorial.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.