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/jakeintech/waybill/syncnpx skills add Jakeintech/waybill --skill syncgit clone --depth 1 https://github.com/Jakeintech/waybillWhat 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.00129 | $0.02532 |
| Opus 5 | $0.00064 | $0.01266 |
| Sonnet 5 | $0.00026 | $0.00506 |
| Haiku 4.5 | $0.00013 | $0.00253 |
Grade A, and why
sync 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync
Pull the objective backbone — issues and merged PRs — from the user's tracker and git host, and reconcile it with the ledger. The reconciliation itself is deterministic: a CLI or MCP tool fetches raw JSON, the engine normalizes and diffs it, you present the plan, one confirmation applies it. Prefer CLIs (acli, gh) over MCP tools for the fetch: the same facts arrive with scoped fields in a fraction of the payload, saved to files instead of flowing through context.
Invoke the engine as "${CLAUDE_PLUGIN_ROOT}/bin/waybill" <command>.
Scope rule (non-negotiable)
Query only the current user's own items: issues assigned to them, PRs
authored by them, in the projects/repos listed in config.json. Never
fetch, store, or summarize individual colleagues' issues, PRs, or
statistics, even on request — explain briefly per
skills/ledger/references/methodology.md §6 and continue with the user's
own data.
Procedure
-
Read
config.jsonforproject_keys,repos,default_branch, andlast_sync, andidentity.jsonfor the identity map. Iflast_syncis null, default the window to the last 90 days and say so. Ifidentity.jsonlacksjira_account_idand the Atlassian MCP is connected, fetch the current user's accountId once and write it back — future queries stay scoped to it. (The acli path needs no accountId:currentUser()in the JQL scopes the fetch at the source.) -
Tracker — Jira. Two fetch paths; prefer the CLI when it is authenticated (
acli jira auth statusexits 0 —waybill statusalso reports this):acli (Atlassian CLI) — preferred. Two steps keep the payload minimal: search returns only keys, then each item is fetched with exactly the fields sync needs (search's flattened JSON cannot carry custom fields;
viewis REST-shaped and can):acli jira workitem search --json --limit 200 --fields key \ --jql 'assignee = currentUser() AND project IN (<keys>) AND updated >= "<date>"' \ > /tmp/waybill-keys.json # .issues? (with ?) also handles a bare-array payload without erroring: jq -r '(.issues? // .) | .[].key' /tmp/waybill-keys.json | while read -r KEY; do acli jira workitem view "$KEY" --json --fields \ "summary,status,resolutiondate,created,updated,issuetype,parent,assignee,customfield_10016,customfield_10026,customfield_10002,customfield_10020,customfield_10010,customfield_10014,customfield_10011" done | jq -s '.' > /tmp/waybill-items.json
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.
- yesterday First seen · 188 lines · 129 tokens per session scan A 70b6b48202f9
sync is a skill published in the GitHub repository Jakeintech/waybill (1 stars, last pushed 9d ago), licensed MIT. It adds 129 tokens to every session and 2,532 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
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
model-compatibility
Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.
flux-txt2img
Build Flux txt2img workflows with Flux.1 Dev (SRPO), Flux 2 Klein 9B, Turbo LoRAs, FluxGuidance, and DualCLIPLoader patterns.
panel-node-pack-sync
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (installcomfyui (action:"selfupdate"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way…
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
31-offer-design-global
Use when the WHAT being sold needs work, not the price and not the copy — core promise, value stack, bonuses, guarantee and risk reversal, honest scarcity and urgency, tier packaging, upsell and downsell paths, and high-ticket or productized service structures. Trigger on 'design an offer', 'irresistible offer'…