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/artivilla/agents-config/githubnpx skills add artivilla/agents-config --skill githubgit clone --depth 1 https://github.com/artivilla/agents-configWhat 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.00040 | $0.00980 |
| Opus 5 | $0.00020 | $0.00490 |
| Sonnet 5 | $0.00008 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
github 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues Manager
Complete GitHub issue management using the gh CLI tool. This Skill provides comprehensive capabilities for creating, viewing, updating, and managing GitHub issues.
Capabilities
- Create issues - Create new GitHub issues with context from conversations
- List issues - View and filter issues by state, labels, assignees
- View issues - Display full issue details including comments
- Update issues - Modify titles, bodies, labels, and assignees
- Close issues - Close issues with optional closing comments
- Assign issues - Assign issues to team members
Quick Reference
For detailed instructions on each operation, see:
- CREATE_ISSUE.md - Creating new issues
- LIST_ISSUES.md - Listing and filtering issues
- VIEW_ISSUE.md - Viewing issue details
- UPDATE_ISSUE.md - Updating existing issues
- CLOSE_ISSUE.md - Closing issues
- ASSIGN_ISSUE.md - Assigning issues to users
Common Workflows
Bug reporting workflow
- User reports a bug in conversation
- Create issue with
/create-issueor ask me to create one - Issue is created with context from our discussion
- Assign to appropriate team member
- Add labels (bug, priority, etc.)
Issue triage workflow
- List open issues with filters
- View specific issues for details
- Update labels and assignments
- Close resolved issues with status updates
Sprint planning workflow
- List issues by label or milestone
- Assign issues to team members
- Update priorities and estimates
- Track progress through status updates
Critical Instructions
REQUIRED: Before executing ANY GitHub issue operations, you MUST load the relevant reference file(s) using the Read tool. These references contain essential command patterns, parameters, and workflows that are NOT included in this overview.
When the user asks to work with GitHub issues:
- Identify the operation they want to perform (create, list, view, update, close, assign)
- MANDATORY: Load the relevant reference file(s) using the Read tool BEFORE executing any commands:
- Creating issues → Read
CREATE_ISSUE.mdFIRST - Listing issues → Read
LIST_ISSUES.mdFIRST - Viewing issues → Read
VIEW_ISSUE.mdFIRST - Updating issues → Read
UPDATE_ISSUE.mdFIRST - Closing issues → Read
CLOSE_ISSUE.mdFIRST - Assigning issues → Read
ASSIGN_ISSUE.mdFIRST
- Creating issues → Read
- Execute the gh CLI commands following the exact patterns from the loaded reference
- Use temporary files for issue bodies to avoid markdown conflicts (as specified in references)
- Confirm actions and display results
What ships with it
6 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.
- yesterday First seen · 105 lines · 40 tokens per session scan A 219135972e51
github is a skill published in the GitHub repository artivilla/agents-config (0 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 980 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-31.
Other skills, from other repositories
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
wiki-capture
Route anything into the Obsidian vault (second brain) — a thought, URL, concept, snippet, or the 00 INBOX backlog. Use when the user says "add to my wiki", "capture this", "note this down", "save to vault", "process my inbox" — and also on wiki-free phrasings like "jot this down", "remember this idea", "TIL"…
note
Use when working with files in /Notes (the user's Obsidian vault). Covers vault structure (PARA), file naming, frontmatter, icons, templates, kanban boards, and the obsidian CLI.
drupaltools-patch
Apply a patch to a Drupal contrib module or theme from any source — a URL, a Drupal.org issue, an issue comment, a GitLab merge request, a git commit hash, a local file, or a natural language description. Use this skill whenever the user wants to patch a Drupal contrib project, mentions a Drupal.org issue number, a…
backlog
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.
sprint
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.