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/lwalden/aiagentminder/sync-issuesnpx skills add lwalden/AIAgentMinder --skill sync-issuesgit clone --depth 1 https://github.com/lwalden/AIAgentMinderWhat 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.00007 | $0.00927 |
| Opus 5 | $0.00003 | $0.00464 |
| Sonnet 5 | $0.00001 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
sync-issues 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aiagentminder:sync-issues - Sync Sprint Issues to GitHub
Push the current sprint's issues to GitHub Issues for visibility outside Claude Code.
Run this after sprint planning is approved, or at any point to bring GitHub Issues in sync with the current sprint state.
Prerequisites
- A GitHub remote must be configured (
git remote -vshows anoriginpointing to a GitHub repo) ghCLI must be installed and authenticated (gh auth status)- An active sprint must exist in
SPRINT.md(**Status:** in-progressorproposed)
Step 1: Validate Prerequisites
git remote -v
gh auth status
- If no GitHub remote: stop. "No GitHub remote found. Add one with
git remote add origin <url>first." - If
ghnot authenticated: stop. "GitHub CLI not authenticated. Rungh auth loginfirst." - If no SPRINT.md or no active sprint: stop. "No active sprint found. Run a sprint first, then sync."
Step 2: Read Current Sprint
Read SPRINT.md. Extract:
- Sprint number (e.g.,
S1) - Sprint goal
- Each issue: ID, title, type, risk flag, status
Step 3: Check Existing GitHub Issues
gh issue list --label "aiagentminder" --json number,title,state,labels --limit 100
Build a map of existing issues by their sprint ID label (e.g., label S1-001).
Step 4: Create or Update Issues
For each sprint issue:
If no matching GitHub issue exists (no issue with label matching the sprint issue ID):
gh issue create \
--title "[S{n}-{seq}] {title}" \
--body "{body}" \
--label "aiagentminder,sprint-S{n},{type}" \
[--label "risk" if risk-tagged]
Body format:
**Sprint:** S{n} — {sprint goal}
**Type:** {feature | fix | chore | spike}
**Status:** {todo | in-progress | done | blocked}
{acceptance criteria if available from sprint planning}
If a matching GitHub issue exists:
- If sprint status is
doneand GitHub issue is open: close it.gh issue close {number} --comment "Completed in sprint S{n}." - If sprint status is
blockedand GitHub issue is open: add a comment.gh issue comment {number} --body "⚠ Blocked: {blocked reason if known}" - If sprint status changed but issue is already in the right state: skip.
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 · 123 lines · 7 tokens per session scan A 78fec67c5891
sync-issues is a skill published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 927 once invoked, about $0.0000 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
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…
predictor-hand-skill
Expert knowledge for AI forecasting — superforecasting principles, signal taxonomy, confidence calibration, reasoning chains, and accuracy tracking.
getting-started
Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.
github
Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
ci-cd
CI/CD pipeline expert for GitHub Actions, GitLab CI, Jenkins, and deployment automation.