Borrowing it
Nothing to install: this file belongs to martin-francois/symphony-trello. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/martin-francois/symphony-trello/main/.codex/skills/issue-sweep/SKILL.mdgit clone --depth 1 https://github.com/martin-francois/symphony-trelloWrote 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/martin-francois/symphony-trello/issue-sweep)<a href="https://agentmods.dev/skills/martin-francois/symphony-trello/issue-sweep"><img src="https://agentmods.dev/badge/skills/martin-francois/symphony-trello/issue-sweep/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/martin-francois/symphony-trello/issue-sweep"><img src="https://agentmods.dev/badge/skills/martin-francois/symphony-trello/issue-sweep.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.00067 | $0.00623 |
| Opus 5 | $0.00034 | $0.00311 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
issue-sweep 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 11d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Sweep
This skill is a thin dispatcher. The canonical policy lives in
../../../docs/agents/github-issue-triage.md; do not duplicate the label matrix
or issue editing rules here.
Workflow
- Read
../../../docs/agents/github-issue-triage.mdcompletely before fetching or editing issues. Treat it as the source of truth for sweep scope, issue-body updates, labels, dependencies, compatibility decisions, and already-implemented checks. - Confirm GitHub authentication and repository context with the active
repository-approved GitHub tooling, such as the helper or app named by
.tessl/RULES.mdand installed GitHub skills. Do not use directghwhere those rules require helper or app access. If authentication is missing or editing is not permitted, report the blocker and do not pretend the sweep was completed. - Fetch all open issues, including title, body, labels, milestone, assignees, assignment timeline events, linked or referencing open pull requests, and relevant comments. Do not limit the sweep to examples named by the user.
- Apply the canonical triage document in cycles. After making any change, fetch the open issue set again and repeat until one full pass finds no body, label, milestone, dependency, already-implemented, or relationship changes.
- When creating follow-up issues during the sweep, use the repository issue templates and the same full triage policy before publishing the issue.
- Prefer editing maintainer-authored issue bodies over adding comments, unless the canonical triage document calls for a historical comment or the issue was opened by another account.
- Finish with a concise report: number of cycles, issues changed, issues intentionally left unchanged, labels or dependencies repaired, users assigned from pickup comments, stale assigned issues with no open pull request, issues closed as already implemented, and any blockers.
Checks
- Run the live invariant checks needed by
../../../docs/agents/github-issue-triage.mdfor the policy areas touched during the sweep. - If the sweep changes repo files, run the relevant local documentation or code checks before committing.
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.
- 11d ago First seen · 60 lines · 67 tokens per session scan A e1e509d774cb
issue-sweep is a skill published in the GitHub repository martin-francois/symphony-trello (2 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 623 once invoked, about $0.0003 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
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.