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/jondoescoding/jondoescoding-coding-rulesWrote 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/jondoescoding/jondoescoding-coding-rules/cody-schneider-social-media-methodology)<a href="https://agentmods.dev/rules/jondoescoding/jondoescoding-coding-rules/cody-schneider-social-media-methodology"><img src="https://agentmods.dev/badge/rules/jondoescoding/jondoescoding-coding-rules/cody-schneider-social-media-methodology.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.00000 | $0.00908 |
| Opus 5 | $0.00000 | $0.00454 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
cody-schneider-social-media-methodology 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cody Schneider Social Media Writing Methodology
When creating social media content in markdown files, always apply the Cody Schneider writing style and methodology.
Core Writing Style Rules
Structure & Format
- Use short, punchy lines (1-2 sentences max per line)
- Break up content with line breaks for scannability
- Use lowercase for casual, conversational tone
- No unnecessary capitalization except for proper nouns
- Use bullet points and numbered lists for clarity
Forbidden Elements (Scott Adams Rules)
- Never use hyphens (-) - restructure sentences instead
- Never use em dashes (—) - use commas, periods, or restructure
- Never use the word "like" - replace with:
- "such as" instead of "like"
- "including" instead of "like"
- "for example" instead of "like"
- "similar to" instead of "like"
- Never use emojis in any context
- Remove filler words: very, really, quite, rather, somewhat
- Remove hedge words: I think, I believe, maybe, perhaps
Sentence Construction
- Use active voice always
- Keep sentences short and punchy
- One idea per sentence
- Lead with action or result
- Eliminate unnecessary words ruthlessly
Cody Schneider Content Structure
Hook Patterns
- Bold claim + contradiction
- Problem/solution for target audience
- Personal journey + surprising result
- Direct value promise
- Curiosity gap + expertise
Content Flow
- Strong opening hook - grab attention immediately
- Process or steps - make it actionable
- Personal story/credibility - build trust
- Results or transformation - show proof
- Target audience relevance - make it specific
- CTA with "ps" - natural call to action
Example Structure
**bold hook statement**
here's my exact process for [specific outcome]
step 1: [action]
[brief explanation]
step 2: [action]
[brief explanation]
[personal story or struggle]
[transformation or result]
[specific audience benefit]
ps
[natural CTA with link]
Content Types
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.
- 6d ago First seen · 128 lines · 908 tokens per session scan A c933e0400ae8
cody-schneider-social-media-methodology is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 908 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
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
monitoring
Monitoring, observability, and alerting rules.
documentation-standards
Documentation standards for code, APIs, and architecture.
token-efficiency
Token optimization rules to reduce AI costs by 30%+.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.