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/sabbour/agentweaver/agentweaver-github-issuenpx skills add sabbour/agentweaver --skill agentweaver-github-issuegit clone --depth 1 https://github.com/sabbour/agentweaverWhat 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.00214 | $0.02520 |
| Opus 5 | $0.00107 | $0.01260 |
| Sonnet 5 | $0.00043 | $0.00504 |
| Haiku 4.5 | $0.00021 | $0.00252 |
Grade A, and why
agentweaver-github-issue 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 2d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Skill
You are filing a GitHub issue and dispatching the right Squad member to act on it. This is the team's primary intake mechanism — every bug Ahmed reports, every feature he requests, every chore he notices flows through here into tracked, routed work.
Step 1 — Classify
Determine the type and domain from the user's description:
| Type | When | type: label |
|---|---|---|
| Bug | Something is broken, behaving wrong, or producing an error | type:bug |
| Feature | New capability, UX improvement, new endpoint or page | type:feature |
| Chore | Cleanup, refactor, rename, remove dead code, dependency update | type:chore |
| Docs | Missing, wrong, or outdated documentation | type:docs |
| Spike | Need to investigate before committing to a solution | type:spike |
| Epic | A large body of work that decomposes into sub-issues | type:epic |
Domain → primary squad assignee (use routing.md for edge cases):
| Domain signals | Primary | Secondary |
|---|---|---|
| API, backend, database, endpoints, git-worktree, assembly | squad:tank |
— |
| MAF, run orchestration, tool loop, CTS, recovery, agent-host | squad:morpheus |
— |
| React UI, Fluent, page, component, frontend, CLI ink | squad:trinity |
— |
| Test, regression, coverage, playwright, vitest | squad:smith |
— |
| AKS, k8s, Docker, CI, build, release, infra | squad:link |
— |
| Docs, security review, prompt injection, sandbox boundary | squad:seraph |
— |
For bugs: always add squad:smith as co-assignee (Smith does RCA).
For multi-domain bugs: assign primary domain owner + squad:smith.
For features/spikes: use the domain owner; if scope is unclear, use squad:smith for research first.
Step 2 — Pick labels
Combine: type:* + squad:* + go:* + priority:* + release:*
go: label (readiness):
go:yes— clear enough to start immediately (bugs, simple chores, well-spec'd features)go:needs-research— needs investigation or spec before coding (complex features, spikes, unclear bugs)go:no— explicitly decided not to pursue (rare — only if user says so)
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.
- 2d ago First seen · 263 lines · 214 tokens per session scan A 8edabd28af08
agentweaver-github-issue is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 2d ago), licensed MIT. It adds 214 tokens to every session and 2,520 once invoked, about $0.0011 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
auditing-kubernetes-cluster-rbac
Auditing Kubernetes cluster RBAC configurations to identify overly permissive roles, wildcard permissions, dangerous ClusterRoleBindings, service account abuse, and privilege escalation paths using kubectl, rbac-tool, KubiScan, and Kubeaudit.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
dotnet-microsoft-agent-framework
Build .NET AI agents and multi-agent workflows with Microsoft Agent Framework using the right agent type, threads, tools, workflows, hosting protocols, and enterprise guardrails.
dotnet-microsoft-extensions-ai
Build provider-agnostic .NET AI integrations with Microsoft.Extensions.AI, IChatClient, embeddings, middleware, structured output, vector search, and evaluation.
dotnet-orleans
Build or review distributed .NET applications with Orleans grains, silos, persistence, streaming, reminders, placement, testing, and cloud-native hosting.
mcaf-dotnet-profiling
Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. Use when a repo needs CPU tracing, live counters, GC and allocation investigation, exception or contention tracing, heap snapshots, or startup diagnostics without GUI-only tooling.