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 juspay/neurolink --skill github-commentinggit clone --depth 1 https://github.com/juspay/neurolinkWrote 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/juspay/neurolink/github-commenting)<a href="https://agentmods.dev/skills/juspay/neurolink/github-commenting"><img src="https://agentmods.dev/badge/skills/juspay/neurolink/github-commenting.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.1 | $0.00041 | $0.00631 |
| Opus 5 | $0.00020 | $0.00316 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
github-commenting 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean GitHub PR commenting
Before posting anything
- List the existing review comments AND issue comments on the pull request first.
- Every comment you post starts with an invisible marker line:
<!-- yama:<stable-finding-id> -->. If a marker for the same finding already exists, do NOT post it again — update that comment if it needs fixing, otherwise leave it alone.
Inline comments
- Anchor to the exact file and line in the DIFF. A line that is not part of the diff cannot hold a comment — anchor to the nearest changed line and say so.
- Multi-line ranges:
start_lineis the first line,lineis the last;side/start_sideareRIGHTfor added lines andLEFTfor deleted ones. - Tool shapes differ: some GitHub MCP servers post an inline comment in one call; the hosted server may require the pending-review lifecycle (create review → add comments → submit). If a pending review is opened it MUST be submitted — both or neither, never half.
Suggestion blocks — a fix the author applies in one click
Explain the issue in one or two sentences ABOVE the block, then:
```suggestion
the replacement for the entire anchored line range
```
- The block's body replaces the WHOLE
start_line..linerange — include every line of the range, exactly indented. - If the replacement itself contains triple backticks (markdown files, code fences), use a four-backtick outer fence (
````suggestion) so GitHub does not close the block early. - Prefer a suggestion block whenever you propose a concrete code fix - it is the fix the author applies in one click, and an inline comment about a code change should normally carry one. Fall back to prose only when the right code is genuinely uncertain.
Formatting for humans
- One finding per comment: severity (CRITICAL / MAJOR / MINOR), what breaks, why it matters here, and the fix.
- Cite rulebook ids where they apply.
- Evidence longer than ~10 lines goes in a collapsible section:
<details><summary>evidence</summary>…</details>. - Prefer short headers, tables and task lists over walls of prose. No emoji noise.
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.
- 3d ago First seen · 49 lines · 41 tokens per session scan A 7e7ac9d3dbaa
github-commenting is a skill published in the GitHub repository juspay/neurolink (129 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 631 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-09-03.
Other skills, from other repositories
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
openclaw-pr-batch-sweep
Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…
open-pr-fix
Act on the findings a review left on a PR or MR: take or decline each by severity, edit the code, one commit, reply. Use when handed a PR or MR URL that has already been reviewed. Edits real code.
commit-changes
A manually triggered process for preparing and making a precise Git commit or push, where Git is the tool used to track code changes.
commit
Read this skill before making git commits.
git-essentials
Essential Git commands and workflows for version control, branching, and collaboration.