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/neverinfamous/memory-journal-mcp/github-commandernpx skills add neverinfamous/memory-journal-mcp --skill github-commandergit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWhat 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.00131 | $0.01668 |
| Opus 5 | $0.00066 | $0.00834 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 131 tokens to every session and 1,668 once invoked, about $0.0007 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
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-implement
Use when implementing a task - follow the plan, check ACs, track progress.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:feedback
Report a bug, request a feature, or send general feedback to the ALIVE team. Collects safe system metadata, shows a preview, and creates a GitHub Issue. Nothing personal leaves the machine, only what you type and anonymous system info.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.