AIBAST Agents Library is a collection of industry-focused AI agent templates accompanied by a local server that connects agents to GitHub Copilot for language-model inference. It helps developers create and run tool-using agents and isolated project environments, with an optional cloud-backed path for persistent memory. The catalogue entries provide the repository's agents, skills, commands, hooks, and instructions.
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 microsoft/aibast-agents-library --skill aibast_shift-plan_plo04git clone --depth 1 https://github.com/microsoft/aibast-agents-libraryWrote 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/microsoft/aibast-agents-library/aibast_shift-plan_plo04)<a href="https://agentmods.dev/skills/microsoft/aibast-agents-library/aibast_shift-plan_plo04"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/aibast_shift-plan_plo04/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/microsoft/aibast-agents-library/aibast_shift-plan_plo04"><img src="https://agentmods.dev/badge/skills/microsoft/aibast-agents-library/aibast_shift-plan_plo04.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.00037 | $0.00675 |
| Opus 5.5 | $0.00015 | $0.00270 |
| Sonnet 5.5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
day-swing-night-production-plan 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Day, swing, and night production plan
Use this skill for requests such as "Translate the current line performance into a day, swing, and night shift plan," "build the three-shift plan," or "how should we staff the shifts." Cover all three lines and all three shifts.
Inputs (from the packaged synthetic records)
The shift schedule (Day, Swing, Night with hours, operators, premium, start, end) and each line's actual output per hour.
Procedure
- Present the shift schedule: Day (06:00–14:00, 24 operators, 1.0x), Swing (14:00–22:00, 22 operators, 1.0x), Night (22:00–06:00, 18 operators, 1.15x premium). Each shift is 8 hours.
- Compute planned output per line and shift: Day and Swing = actual_uph × 8;
Night = round(actual_uph × 8 × 0.9) at 90% efficiency. Fixed results:
- Electronics Assembly Line A: Day 1,136 / Swing 1,136 / Night 1,022 / Daily Total 3,294.
- Metal Fabrication Line B: Day 2,088 / Swing 2,088 / Night 1,879 / Daily Total 6,055.
- Polymer Molding Line C: Day 1,344 / Swing 1,344 / Night 1,210 / Daily Total 3,898.
- Show operator allocation: 64 total operators across shifts, 3 lines, 7.1 average operators per line per shift.
- Note that the Night shift runs at 90% efficiency and carries a 1.15x labor premium — surface this as the cost/tradeoff of the night shift.
- If asked, add the weekly capacity view (5/6/7 operating days) from the full-24-hour daily figures.
Output
A shift-schedule table, a planned-output-by-line-and-shift table with the Day/Swing/Night columns and Daily Total, and the operator-allocation summary.
Grounding and safety
- Use only the packaged schedule and output figures; never invent shifts, operators, or lines.
- The Daily Total (Night at 90%) is intentionally lower than the full-24-hour Output/Day figure — do not conflate them.
- The plan is a synthetic projection to evaluate, not a committed schedule or a staffing order.
- Never say you lack access and never ask the user to name a line.
- End with:
> Synthetic pilot data; figures are planning estimates, not a live ERP, IoT, or Power BI reading.
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.
- 1mo ago First seen · 58 lines · 37 tokens per session scan A 812bc6b6997d
day-swing-night-production-plan is a skill published in the GitHub repository microsoft/aibast-agents-library (8 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 675 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.