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 ivegamsft/basecoat --skill backlog-rebalance-enginegit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/backlog-rebalance-engine)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/backlog-rebalance-engine"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/backlog-rebalance-engine.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.00075 | $0.00653 |
| Opus 5 | $0.00037 | $0.00327 |
| Sonnet 5 | $0.00015 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
backlog-rebalance-engine 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.
What it actually says
Backlog Rebalance Engine — Project Sync Skill
Use this skill to onboard mapped backlog items into GitHub Project views and keep item status and delivery metadata aligned with the current rebalance plan.
Use Cases
- Sync rebalanced issues into a GitHub Project board after a sprint rebalance run.
- Update existing project items instead of creating duplicates.
- Apply policy-validated metadata mutations for
priority:*,sprint:*, andwave:*. - Emit sync summary plus rollback and reason-coded change log artifacts.
Reference Files
| File | Purpose |
|---|---|
references/project-sync-workflow.md |
Contract and workflow |
scripts/project-sync.sh |
Bash implementation |
scripts/project-sync.ps1 |
PowerShell implementation |
Metadata Mutation Contract
- Allowed families:
priority:*,sprint:*,wave:*, plus projectStatus. - Deterministic apply: remove existing family labels, then add one target label.
- Validation before apply:
priority:(critical|high|medium|low),sprint:<number>,wave:<number>. - Freeze mode blocks metadata label writes unless an explicit override is supplied.
- Each issue includes reason codes (for example
ADD_TO_PROJECT,STATUS_MISMATCH,METADATA_MUTATION_PRIORITY,POLICY_FREEZE_WINDOW_BLOCK).
Sync Report Format
After each run:
Sync complete: added=<n> updated=<n> skipped=<n>
-
added — items inserted (not previously on the board).
-
updated — items whose status field was changed.
-
skipped — items already aligned; no change made.
-
Rollback artifact (JSON) with inverse operations for applied mutations.
-
Change log (JSON) with per-item reason codes and mutation decisions.
Idempotency Contract
A second run on unchanged data must report added=0 updated=0.
What ships with it
4 files 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.
- 3d ago First seen · 79 lines · 75 tokens per session scan A 0943fbe0ae98
backlog-rebalance-engine is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 653 once invoked, about $0.0004 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
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.