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/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/repo-scaffold)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/repo-scaffold"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/repo-scaffold/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/thatrebeccarae/claude-marketing/repo-scaffold"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/repo-scaffold.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.00043 | $0.01487 |
| Opus 5 | $0.00022 | $0.00744 |
| Sonnet 5 | $0.00009 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
repo-scaffold 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Scaffold
Initialize GitHub repositories with standard files and configuration. This skill generates LICENSE, CONTRIBUTING.md, SECURITY.md, CODEOWNERS, .gitignore, .editorconfig, YAML-based issue templates, PR template, CI config skeleton, and optional safety files. It detects project type from existing files and adapts all templates accordingly.
When to Use
This skill should be used when:
- Setting up a new GitHub repository from scratch
- Adding missing standard files to an existing repository
- Standardizing repository configuration across projects
- Preparing a private repo for open-source release
Usage
/repo-scaffold [repo-path] [--license MIT|Apache-2.0|ISC] [--public] [--ci github-actions|none]
| Flag | Default | Description |
|---|---|---|
repo-path |
. (cwd) |
Path to the git repository root |
--license |
MIT |
License type (MIT, Apache-2.0, ISC, GPL-3.0, BSD-2-Clause) |
--public |
off | Include .public-repo, .pii-allowlist, .commit-msg-blocklist |
--ci |
github-actions |
CI provider skeleton (github-actions or none) |
Procedure
Step 1: Validate Repo Path
Confirm the target path is an initialized git repository (contains .git/). If not, halt and inform the user. Never run git init without explicit permission.
Step 2: Scan Existing Files
Inventory the repo root and .github/ directory for any files this skill would generate. Build a conflict list. Never overwrite existing files. If conflicts exist, present them and ask which to skip or replace.
Step 3: Detect Project Type
Identify the primary language and tooling by checking for marker files:
| Marker File | Project Type |
|---|---|
package.json |
Node.js / JavaScript / TypeScript |
pyproject.toml, setup.py, requirements.txt |
Python |
Cargo.toml |
Rust |
go.mod |
Go |
| Multiple markers | Multi-language |
| None of the above | Generic |
If multiple markers are found, treat as multi-language and combine relevant patterns.
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.
- 11d ago First seen · 153 lines · 43 tokens per session scan A 92146d092912
repo-scaffold is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (136 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,487 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-08-30.
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.