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 skills add JSONbored/awesome-claude --skill contributing-to-awesome-claudegit clone --depth 1 https://github.com/JSONbored/awesome-claudeWrote 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/jsonbored/awesome-claude/contributing-to-awesome-claude)<a href="https://agentmods.dev/skills/jsonbored/awesome-claude/contributing-to-awesome-claude"><img src="https://agentmods.dev/badge/skills/jsonbored/awesome-claude/contributing-to-awesome-claude/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/skills/jsonbored/awesome-claude/contributing-to-awesome-claude"><img src="https://agentmods.dev/badge/skills/jsonbored/awesome-claude/contributing-to-awesome-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00209 | $0.01823 |
| Opus 5 | $0.00105 | $0.00911 |
| Sonnet 5 | $0.00042 | $0.00365 |
| Haiku 4.5 | $0.00021 | $0.00182 |
Grade A, and why
contributing-to-awesome-claude 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to awesome-claude (HeyClaude)
HeyClaude is a file-backed directory of Claude/AI workflow resources
(content/<category>/<slug>.mdx) plus a website, registry package, and MCP package that
serve that content. It has two kinds of contribution with two different review
mechanisms — get the kind right first, everything else follows from it.
reference.md (next to this file) has the exhaustive command tables, the two-gate
architecture in detail, the current Codecov numbers, and the content-PR pitfalls. Read it
when a section below tells you to.
Step 0 — Which kind of contribution is this?
| You are... | Contribution type | Review mechanism |
|---|---|---|
Adding/editing one content/<category>/<slug>.mdx entry (agent, MCP server, skill, hook, command, rule, guide, collection, statusline) |
Community content | Private HeyClaude submission gate (one-shot, aggressive) |
Changing apps/web/**, packages/registry/**, packages/mcp/**, scripts/**, workflows |
Platform/code | Standard CI + the shared gittensory-orb bot (advisory) |
These are handled by genuinely different systems (see reference.md §1). Do not mix
them in one PR — CONTRIBUTING.md is explicit that a content PR touches exactly one
content/<category>/<slug>.mdx file, and platform/code changes should stay separate from
individual content imports.
If you're adding a content entry
- Read the schema and examples first:
content/SCHEMA.md(required/optional fields per category) andexamples/content/SUBMISSION_EXAMPLES.md(accepted vs. rejected/rerouted examples — read this before you draft anything non-trivial). - One file, one PR. Add exactly one
content/<category>/<slug>.mdx. Do not touchREADME.md,apps/web/public/data/**,apps/web/src/generated/**,apps/web/src/routeTree.gen.ts, orapps/web/public/downloads/**— those are maintainer-owned generated outputs and editing them in a content PR is a reject reason. - Source-back everything. Canonical source/docs/repo URLs, not affiliate or
tracking links. For hooks, MCP servers, skills, commands, and statuslines, fill
safetyNotes(execution, install, writes, destructive actions, background workers, network access, account writes) andprivacyNotes(local files, logs, credentials, telemetry, retained data) — useprerequisitesonly for setup requirements anddisclosureonly for commercial/listing status, not runtime safety. - A linked issue is genuinely optional here. CONTRIBUTING.md says plainly: "a PR
with no linked issue is fine." Filing your own issue and resolving it is fine too.
What is not fine is multi-account farming (opening an issue on one account,
"resolving" it from another) — see
reference.md§4 for the exact contrast with gittensory/metagraphed's mandatory policy. - Validate narrowly — a content PR does not need the full platform test suite:
Do not runpnpm install --frozen-lockfile pnpm validate:content:strictgenerate:readme/generate:openapior commit build output for a one-file content submission — those are build-time outputs regenerated by CI/deploy. - Understand who actually decides your PR's fate. It is the private submission
gate, not gittensory-orb — see the Step 1 architecture note below and
reference.md§2 for the full disposition table.
What ships with it
1 file 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.
- 11d ago First seen · 129 lines · 209 tokens per session scan A afb802398d7a
contributing-to-awesome-claude is a skill published in the GitHub repository JSONbored/awesome-claude (297 stars, last pushed 25d ago), licensed MIT. It adds 209 tokens to every session and 1,823 once invoked, about $0.0010 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 skills, from other repositories
standup
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
research-archival
Scrape AI research URLs, archive with frontmatter, create GitHub Issues with identity verification.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.