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 XnLemon/Neneko-skill --skill issue-development-loopgit clone --depth 1 https://github.com/XnLemon/Neneko-skillWrote 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/xnlemon/neneko-skill/issue-development-loop)<a href="https://agentmods.dev/skills/xnlemon/neneko-skill/issue-development-loop"><img src="https://agentmods.dev/badge/skills/xnlemon/neneko-skill/issue-development-loop/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/xnlemon/neneko-skill/issue-development-loop"><img src="https://agentmods.dev/badge/skills/xnlemon/neneko-skill/issue-development-loop.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.00137 | $0.01938 |
| Opus 5.5 | $0.00055 | $0.00775 |
| Sonnet 5.5 | $0.00027 | $0.00388 |
| Haiku 4.5 | $0.00014 | $0.00194 |
Grade A, and why
issue-development-loop 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 2mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Development Loop
Own the implementation loop from issue discovery through a clean reviewed pull
request. Treat invocation of this skill as authorization to create a feature
branch, commit the issue work, push that branch to origin, open or update its
pull request, post review comments and replies, and resolve addressed review
threads. Do not merge, close the issue manually, force-push, or modify unrelated
work unless the user explicitly authorizes it.
Required Inputs And Dependencies
Require the user to identify the related issue by URL, repository plus number, or an unambiguous issue reference in the current repository. If multiple issues are declared, build one shared scope only when they are tightly coupled; otherwise process them as separate loops and PRs.
Require an origin remote and authenticated GitHub write access before the
publication phase. Use the GitHub CLI or available GitHub connector according
to repository conventions.
Load and follow both installed skills when their phases begin:
- Use
$neneko-cronly for the delegated review phase, subject to the strict review-only profile below. - Use
$handle-reviewfor the main agent's review-triage and fix phase.
If either dependency is unavailable, stop before that phase and report the missing dependency. Do not silently replace the independent review loop with a local self-review.
Establish The Contract
Before editing code:
- Read the complete issue, linked discussions, acceptance criteria, referenced documents, and relevant repository instructions.
- Inspect the current repository state, default branch, remotes, worktree changes, architecture, tests, and the current code paths implicated by the issue. Preserve unrelated user changes.
- Confirm that the reported problem or requested capability still applies to the current base. Separate the underlying need from any proposed solution in the issue.
- Create an issue ledger containing every required behavior, compatibility constraint, documentation change, test obligation, and explicit non-goal. Record ambiguous or contradictory requirements as blockers rather than guessing across a material product or API decision.
- Split substantial work into coherent development stages. Each stage must be independently testable and must advance the same PR toward the complete issue contract. Keep small issues as a single stage.
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.
- 2mo ago First seen · 178 lines · 137 tokens per session scan A aea459147a55
issue-development-loop is a skill published in the GitHub repository XnLemon/Neneko-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 137 tokens to every session and 1,938 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-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
github
GitHub CLI operations via gh for issues, PRs, Actions, releases, and REST/GraphQL API with --json/--jq parsing. Triggers on: "create an issue", "submit a PR", "check CI status", "why did CI fail", "merge a PR", or pasted GitHub URLs.
project-repo-management
Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval.
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
ensemblr
How Ensemblr works from inside it — the workspace/git-worktree model, the ensemblr control tools and what their answers mean, the committed .ensemblr/settings.toml (setup and run scripts, [git], [prompts], [infisical], environment variables), /.config/ensemblr/config.json, the Changes panel and diff comments, the…