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/nirecom/agents/issue-reconcilenpx skills add nirecom/agents --skill issue-reconcilegit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/issue-reconcile)<a href="https://agentmods.dev/skills/nirecom/agents/issue-reconcile"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-reconcile.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.01167 |
| Opus 5 | $0.00022 | $0.00583 |
| Sonnet 5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
issue-reconcile 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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/issue-close-stage + /issue-close-finalize is the sanctioned close path
inside Claude Code, but the enforce-issue-close.js hook only covers Claude
Code's Bash tool. Issues closed elsewhere have no
<!-- issue-close-sentinel: appended --> comment
and never trigger doc-append. This skill walks closed issues, detects
missing sentinels, and backfills entries.
Usage: /issue-reconcile
Pre-flight
AGENTS_CONFIG_DIRmust be set.- Read
rules/github-issues.md— on-demand-only, never auto-injected.
Step 1: pre-resolve
Resolve in main: OWNER_REPO=$(gh repo view --json owner,name --jq '.owner.login + "/" + .name'), HISTORY_MD_PATH (absolute path to docs/history.md), HISTORY_DIR_PATH (absolute path to docs/history/ directory).
Step 2: scan via worker
Dispatch the issue-reconcile worker per skills/_shared/worker-dispatch.md. Payload: owner_repo, history_md_path, history_dir_path, artifact_dir (the PLANS_DIR from WD-1), limit (omit for the 1000-issue default).
On status: failed: stop and report. A scan truncated at <N> summary means the closed-issue scan hit limit — re-dispatch with a higher limit rather than acting on the partial result. On status: complete: read the JSONL artifact — issues with classification: needs-reconcile feed Step 3.
Step 3: prompt and append
For each non-clean issue, show the user:
- Issue number, title, closedAt
- Classification (sentinel-only / unappended)
- The Background/Changes (or Cause/Fix) the entry would carry
Ask whether to append, skip, or stop.
On "append":
# Fetch current docs/history.md into a staging file, append via --target,
# validate, then PUT to GitHub via the Contents API. The ISSUE_CLOSE_SKILL=1
# env-var bypass was removed in #672.
STAGING_DIR="$(bash "$AGENTS_CONFIG_DIR/bin/workflow-plans-dir")"
STAGE="$STAGING_DIR/reconcile-${NUM}-history.md"
OWNER_REPO=$(gh repo view --json owner,name --jq '.owner.login + "/" + .name')
DEF=$(gh api "repos/$OWNER_REPO" --jq '.default_branch')
gh api "repos/$OWNER_REPO/contents/docs/history.md?ref=$DEF" \
| jq -r '.content' | tr -d '\r\n' | base64 -d > "$STAGE"
bash "$AGENTS_CONFIG_DIR/bin/github-issues/issue-to-history.sh" "$NUM" --target "$STAGE" --allow-backdate
bash "$AGENTS_CONFIG_DIR/bin/lib/github-contents-write.sh" \
--owner "${OWNER_REPO%%/*}" --repo "${OWNER_REPO#*/}" \
--path docs/history.md --file "$STAGE" \
--message "docs(history): record issue #$NUM" --branch "$DEF"
rm -f "$STAGE"
What ships with it
1 file 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.
- 4d ago First seen · 98 lines · 44 tokens per session scan A a8bb0fa236e8
issue-reconcile is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,167 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.