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 agentmods add skills/netresearch/github-project-skill/github-projectnpx skills add netresearch/github-project-skill --skill github-projectgit clone --depth 1 https://github.com/netresearch/github-project-skillWhat 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 | $0.00082 | $0.01188 |
| Opus 5 | $0.00041 | $0.00594 |
| Sonnet 5 | $0.00016 | $0.00238 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
github-project 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
45 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.
- assets/auto-merge-direct.yml.template 4.5 KB
- assets/auto-merge-queue.yml.template 2.4 KB
- assets/auto-merge.yml.template 1.8 KB
- assets/branch-protection.json.template 483 B
- assets/bug_report.md.template 725 B
- assets/CODEOWNERS.template 937 B
- assets/CONTRIBUTING.md.template 3.2 KB
- assets/dependabot.yml.template 1.1 KB
- assets/feature_request.md.template 1.2 KB
- assets/pr-quality.yml.template 1.8 KB
- assets/PULL_REQUEST_TEMPLATE.md.template 1.2 KB
- assets/release-labeler.yml.template 12 KB
- assets/renovate.json.template 654 B
- assets/SECURITY.md.template 2.2 KB
- checkpoints.yaml 24 KB
- evals/evals.json 9.1 KB
- references/actionlint-guide.md 13 KB
- references/actions-upgrade-guide.md 5.0 KB
- references/agentic-workflows.md 7.1 KB
- references/ai-reviewer-pushback.md 13 KB
- references/auto-merge-guide.md 33 KB
- references/branch-migration.md 2.9 KB
- references/ci-runner-capacity.md 5.3 KB
- references/cross-repo-references.md 2.0 KB
- references/dependency-management.md 30 KB
- references/gh-cli-reference.md 19 KB
- references/merge-strategy.md 37 KB
- references/multi-repo-operations.md 21 KB
- references/no-editorializing.md 229 B
- references/org-security-settings.md 5.0 KB
- references/pages-and-collector-workflows.md 9.4 KB
- references/pr-commit-cleanup.md 2.4 KB
- references/release-labeling.md 7.0 KB
- references/repo-bootstrap.md 10 KB
- references/repo-setup-guide.md 6.3 KB
- references/repository-structure.md 6.4 KB
- references/reusable-workflow-pitfalls.md 17 KB
- references/reusable-workflow-security.md 13 KB
- references/security-config.md 29 KB
- references/sub-issues.md 4.1 KB
- references/tag-validation.md 12 KB
- references/upstream-contributions.md 3.5 KB
- references/workflow-bash-patterns.md 11 KB
- scripts/init-branch-protection.sh 12 KB runs code
- scripts/verify-github-project.sh 26 KB runs code
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.
- yesterday First seen · 125 lines · 82 tokens per session scan A f1e67ffe7676
github-project is a skill published in the GitHub repository netresearch/github-project-skill (7 stars, last pushed yesterday), with no licence file. It adds 82 tokens to every session and 1,188 once invoked, about $0.0004 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-31.
Other skills, from other repositories
sanctuary
Security, custody, and privacy infrastructure for AI agents. Use when the agent needs encrypted state storage, self-custodied identity, selective disclosure, zero-knowledge proofs, portable reputation, sovereignty health reporting, handshakes, MCP-to-MCP federation, protection-posture auditing, or principal dashboard…
git-workflow
Use when establishing branching strategies, implementing Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (including CI verification, auto-merge queues, and post-merge cleanup), managing PR review threads, merging PRs with signed commits, handling merge conflicts, verifying a…
security-audit
Use when conducting security assessments — OWASP Top 10 / API / LLM, CWE Top 25, CVSS scoring — auditing PHP/TYPO3, APIs, frontend, Terraform/K8s/Docker IaC, AWS cloud, AI agent configs, or scanning dependencies.
skill-repo
Use when creating skill repositories, standardizing or validating skill repo structure, setting up composer/release workflows, configuring split licensing (MIT + CC-BY-SA-4.0), fixing plugin.json / SKILL.md validation or version-parity errors, or releasing a skill version (version bump, tagging).
go-development
Use when developing Go applications, implementing job schedulers or cron (netresearch/go-cron, ofelia), Docker API integrations, LDAP/AD clients, building resilient services with retry logic, setting up Go test suites (unit/integration/fuzz/mutation), or running golangci-lint.
typo3-extension-upgrade
Use when upgrading TYPO3 extensions to newer LTS versions (v11->v12, v12->v13, v13->v14 - v14.3 LTS is the current target), running Extension Scanner, Rector, Fractor, PHPStan, fixing deprecated APIs, or resolving compatibility issues. Also triggers on: migration, version upgrade, deprecated API, dual-version…