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/itallstartedwithaidea/gemini-cli-googleadsagent/pr-address-commentsnpx skills add itallstartedwithaidea/gemini-cli-googleadsagent --skill pr-address-commentsgit clone --depth 1 https://github.com/itallstartedwithaidea/gemini-cli-googleadsagentWrote 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/itallstartedwithaidea/gemini-cli-googleadsagent/pr-address-comments)<a href="https://agentmods.dev/skills/itallstartedwithaidea/gemini-cli-googleadsagent/pr-address-comments"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/gemini-cli-googleadsagent/pr-address-comments.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.00036 | $0.00227 |
| Opus 5 | $0.00018 | $0.00113 |
| Sonnet 5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
pr-address-comments 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.
This is a copy
100% identical to pr-address-comments — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are helping the user address comments on their Pull Request. These comments may have come from an automated review agent or a team member.
OBJECTIVE: Help the user review and address comments on their PR.
Comment Review Procedure
- Run the
scripts/fetch-pr-info.jsscript to get PR info and state. MAKE SURE you read the entire output of the command, even if it gets truncated. - Summarize the review status by analyzing the diff, commit log, and comments to see which still need to be addressed. Pay attention to the current user's comments. For resolved threads, summarize as a single line with a ✅. For open threads, provide a reference number e.g. [1] and the comment content.
- Present your summary of the feedback and current state and allow the user to guide you as to what to fix/address/skip. DO NOT begin fixing issues automatically.
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 · 14 lines · 36 tokens per session scan A 96ffbdccdbc2
pr-address-comments is a skill published in the GitHub repository itallstartedwithaidea/gemini-cli-googleadsagent (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 227 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pr-address-comments, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
collaboration-intelligence
Maintain and use a cross-channel collaboration map of rooms, people, agents, agent owners, relationships, expertise, ownership, roster, priority/VIP handling, and recent context. Trigger when a task or message carries room/channel/sender/member metadata; the user asks who is in a room, what it is for, who owns or…
schedule-crons
Re-create all session cron jobs for Sutando. Run this on startup or after a session restart.
task-orphan-check
Resolve orphan tasks left in /tasks/ from a previous session that crashed mid-execution. Classifies each live task as done / fresh / stale by cross-referencing per-side-effect markers, then archives or recovers as appropriate. Runs once on startup; safe to re-invoke.
agent-room-ops
One skill, multiple tools. Everything an agent does in a room beyond its task inbox lives here as a tool, so the parity capabilities are self-evidently one collection (not N scattered skills). Each tool is a thin gateway-only client verb sharing gateway.py; the gateway/broker (box-side) owns the platform creds and…
engine-conflict-resolve
Ask Sutando to resolve a conflicted update of a Sutando checkout. When pulling the latest release/main conflicts with local changes, Sutando reproduces the merge in a scratch git worktree, resolves the conflicts there, proposes the resolution to the owner, and fast-forwards the live checkout only after explicit…
claude-codex
Bash wrapper around the local Codex CLI for non-interactive runs from inside Sutando (bridges, cron, scripts). For interactive code review or task hand-off from this Claude Code session, prefer the official /codex: plugin commands; this skill is the file-bridge-compatible path that discord-bridge.py invokes for…