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 The-AI-Directory-Company/agents-and-skills --skill open-source-contributing-guidegit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/open-source-contributing-guide)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/open-source-contributing-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/open-source-contributing-guide/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/the-ai-directory-company/agents-and-skills/open-source-contributing-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/open-source-contributing-guide.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.00036 | $0.01303 |
| Opus 5 | $0.00018 | $0.00651 |
| Sonnet 5 | $0.00007 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
open-source-contributing-guide 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 9d 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.
Open Source Contributing Guide
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- What is the project? (Name, language, framework, repo URL)
- What is the project's maturity? (New, established with existing norms, large ecosystem)
- What contributions are welcome? (Code, docs, tests, design, translations, triage)
- What is the tech stack? (Languages, build tools, test frameworks, CI/CD)
- What is the governance model? (Solo maintainer, core team, foundation-backed)
- What license does the project use? (MIT, Apache 2.0, GPL, etc.)
If the user says "we just need a CONTRIBUTING.md," clarify: a contributing guide without working setup instructions and clear PR expectations creates frustrated contributors who never return.
Contributing guide template
1. Welcome and Orientation
# Contributing to [Project Name]
## Ways to Contribute
- **Report bugs** — File an issue with a reproduction case
- **Fix bugs** — Pick up issues labeled `good first issue` or `help wanted`
- **Add features** — Discuss in an issue before starting work
- **Improve docs** — Fix typos, add examples, clarify explanations
- **Write tests** — Increase coverage, add edge cases
- **Review PRs** — Constructive feedback on open pull requests
## Before You Start
1. Read our [Code of Conduct](CODE_OF_CONDUCT.md)
2. Check [existing issues](link) to avoid duplicate work
3. For features or large changes, open an issue first
Keep this section short. Contributors decide within 60 seconds whether to keep reading.
2. Development Setup
Write setup instructions that work on a fresh machine. Include prerequisites (language version, package manager), fork-and-clone steps, dependency installation, environment setup, and a command to run the test suite that verifies the setup works.
Include a troubleshooting table for known setup issues (common error messages with specific fixes). Every setup problem a contributor solves alone is a contributor who almost left.
What ships with it
5 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.
- 9d ago First seen · 128 lines · 36 tokens per session scan A de507064b8d3
open-source-contributing-guide is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,303 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-09-03.
Other skills, from other repositories
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
shipping-a-pr
Use when finished work needs to ship as a pull request, or when the ask is about a PR — creating one, bringing it up to date, adding screenshots, watching its checks, or addressing its review comments. Not for reviewing a PR you are not shipping.
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.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.