Borrowing it
Nothing to install: this file belongs to opencue/cuecards. 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/opencue/cuecards/main/.agents/skills/github-optimization/SKILL.mdgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/skills/opencue/cuecards/github-optimization)<a href="https://agentmods.dev/skills/opencue/cuecards/github-optimization"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/github-optimization.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.00155 | $0.04682 |
| Opus 5 | $0.00077 | $0.02341 |
| Sonnet 5 | $0.00031 | $0.00936 |
| Haiku 4.5 | $0.00015 | $0.00468 |
Grade A, and why
github-optimization 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 3d 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository Optimization
Transform any GitHub repository into a high-converting, SEO-optimized landing page that drives stars, followers, and traffic. Every repo you touch should look like a top-100 open source project.
This skill has two modes:
- Optimize — rewrite a repo's README, metadata, and structure for maximum conversion
- Advise — give the user a star growth strategy using the knowledge base below
Goals (in priority order)
- Stars -- the primary social proof metric on GitHub
- Followers -- drive traffic to the repo owner's social profiles
- Discoverability -- rank in GitHub search, Google, and LLM answer engines
- Traffic -- turn visitors into users/followers
- Professional credibility -- signal quality through structure and polish
Step 0: User Configuration (Self-Updating)
Before optimizing, you need to know who owns this repo. This step runs once -- after that, the config is reused.
Check for existing config
Look for ~/.Codex/skills/github-optimization/.config.yml. If it exists, load the values and skip to Step 1. Show the user what's loaded and ask if anything changed.
If no config exists, detect + ask
-
Detect automatically from git config and GitHub API:
gh api user-- gets the authenticated GitHub username and profile URLgh api repos/<owner>/<repo>-- gets the repo owner (could be org or user)git config user.name-- gets the local git display name
-
Ask the user for anything you can't detect:
- Display name -- their real name or preferred attribution (e.g., "Jane Smith")
- X/Twitter handle -- for the Follow badge (e.g., "@janesmith"). If they don't want it, skip it.
- Company or organisation -- for footer attribution (optional)
- Company URL -- link for the company name (optional)
- Website URL -- personal or company site (optional)
-
Save the config to
~/.Codex/skills/github-optimization/.config.yml:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 459 lines · 155 tokens per session scan A b524e39018ea
github-optimization is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 4,682 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…