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 neverinfamous/memory-journal-mcp --skill github-commandergit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/github-commander)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/github-commander"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/github-commander/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/neverinfamous/memory-journal-mcp/github-commander"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/github-commander.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.00131 | $0.01668 |
| Opus 5.5 | $0.00052 | $0.00667 |
| Sonnet 5.5 | $0.00026 | $0.00334 |
| Haiku 4.5 | $0.00013 | $0.00167 |
Grade A, and why
github-commander 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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Commander
Structured, configurable workflows that teach AI agents to triage GitHub issues, review PRs, and sprint through milestones. Every action is journaled for full audit trails, and human-in-the-loop checkpoints keep you in control.
The reason every step journals its results is that it creates a searchable audit trail — future sessions can find exactly what was tried, what passed, and what failed, without the human needing to remember or repeat context.
When to Load
Load this skill when any of these apply:
- You are assigned or asked to fix a GitHub issue
- You need to review or submit a pull request
- You need to work through issues in a milestone
- You want to run dependency updates, security audits, or code quality audits
- The user mentions an issue number (e.g., "fix #42") or PR number
- The user says "triage", "audit", "review", "update deps", or similar
- You are about to push code and want a structured validation pipeline
Quick Reference
| Workflow | File | Purpose |
|---|---|---|
| Issue Triage | workflows/issue-triage.md |
Fix a single GitHub issue end-to-end |
| PR Review | workflows/pr-review.md |
Review a PR with validation pipeline |
| Milestone Sprint | workflows/milestone-sprint.md |
Work through milestone issues sequentially |
| Roadmap Kickoff | workflows/roadmap-kickoff.md |
Translate planning epics into Kanban issues |
| Update Dependencies | workflows/update-deps.md |
Dependency update with audit trail |
Prerequisites
ghCLI authenticated (gh auth status)GITHUB_TOKENset for API accessPROJECT_REGISTRYconfigured for repo auto-detection- Project repo cloned locally
Configuration
All commands are configurable via environment variables. Defaults assume a Node.js project. Override for other ecosystems (Python, Rust, Go, etc.).
What ships with it
10 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.
- config/project-config.example.md 2.9 KB
- workflows/code-quality-audit.md 3.4 KB
- workflows/copilot-audit.md 2.9 KB
- workflows/issue-triage.md 6.4 KB
- workflows/milestone-sprint.md 2.5 KB
- workflows/perf-audit.md 4.0 KB
- workflows/pr-review.md 3.5 KB
- workflows/roadmap-kickoff.md 3.6 KB
- workflows/security-audit.md 4.9 KB
- workflows/update-deps.md 3.5 KB
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.
- 1mo ago First seen · 145 lines · 131 tokens per session scan A b387472a3fe8
github-commander is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 2mo ago), licensed MIT. It adds 131 tokens to every session and 1,668 once invoked, about $0.0005 per session on Opus 5.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
review-before-commit
Run a behavioral self-check before persisting story results. Verifies diff simplicity, scope adherence, and verifiable completion against enso §10 behavioral principles. Use when a story's implementation is complete and ready to close.
gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
github
Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".
address-pr-feedback
Unified PR feedback workflow - collect, triage, and fix review comments in a single command.
git-conventions
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit…
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, or verify PR readiness. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user…