Borrowing it
Nothing to install: this file belongs to sabbour/agentweaver. 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/sabbour/agentweaver/dev/.copilot/skills/agentweaver-issue-status/SKILL.mdgit clone --depth 1 https://github.com/sabbour/agentweaverWrote 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/sabbour/agentweaver/agentweaver-issue-status)<a href="https://agentmods.dev/skills/sabbour/agentweaver/agentweaver-issue-status"><img src="https://agentmods.dev/badge/skills/sabbour/agentweaver/agentweaver-issue-status.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.00129 | $0.01312 |
| Opus 5 | $0.00064 | $0.00656 |
| Sonnet 5 | $0.00026 | $0.00262 |
| Haiku 4.5 | $0.00013 | $0.00131 |
Grade A, and why
agentweaver-issue-status 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Status Board
You are producing a pipeline status table for GitHub issues in this repo. The goal is to give the user an at-a-glance view of where each issue stands across the full lifecycle: filed → committed → merged → deployed → documented.
Run the bundled script to collect all data, then render the table.
Step 1 — Run the data collection script
python .copilot/skills/agentweaver-issue-status/scripts/collect.py \
--repo sabbour/agentweaver \
[--filter bugs|features|chores|open|closed|all] \
[--squad trinity|tank|smith|morpheus|link|seraph]
The script outputs a JSON array of issue records. Each record has:
number,title,agents(list of squad member names),statuscommit(SHA of the commit mentioning this issue, or null)deployed(true/false/null — null means unknown)docs(true/false/null — true if docs were updated, false if needed, null if N/A)pr_number,pr_state(open/merged/null)
If the script isn't available or fails, collect the data manually:
gh issue list --state all --limit 30 --json number,title,labels,stategit log --oneline -50— scan for#Nreferences to find commitsgh pr list --state all --json number,title,state,mergedAt,headRefName— find PRs per issue- Check the live deployment's image tag and provenance with the current Node.js
toolchain (
scripts/azure/variables.mjs,scripts/azure/provision-infra.mjs) or the cluster's workload metadata. Do not use the removedscripts/aks/shell scripts. Resolve the deployed tag to its Git ref, then rungit log {deployed_sha}..HEAD --oneline— issues whose commits appear here are not yet deployed.
Step 2 — Determine status for each issue
Use this decision tree:
| Condition | Status label | Emoji |
|---|---|---|
| Issue closed, merge commit found | {short_sha} |
✅ |
| Issue closed, no commit found | closed |
✅ |
| Issue open, PR merged to main | merged |
✅ |
| Issue open, PR open | in review |
🔄 |
| Issue open, commit on branch (no PR yet) | implementing |
🔄 |
Issue open, squad:smith is sole assignee |
RCA in progress |
🔍 |
Issue open, go:needs-research label |
needs research |
🔍 |
Issue open, go:yes, no activity |
backlog |
📋 |
Issue open, go:no |
on hold |
⏸️ |
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.
- 6d ago First seen · 108 lines · 129 tokens per session scan A be9de9f4cdf0
agentweaver-issue-status is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed yesterday), licensed MIT. It adds 129 tokens to every session and 1,312 once invoked, about $0.0006 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
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
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.
project-tasks
Use this protocol to create, update, execute, or complete the structured projecttasks backlog in a Project conversation.
swarm-orchestration
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.