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/comisai/comis/precision-apiarynpx skills add comisai/comis --skill precision-apiarygit clone --depth 1 https://github.com/comisai/comisWhat 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.00081 | $0.00765 |
| Opus 5 | $0.00041 | $0.00382 |
| Sonnet 5 | $0.00016 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
apiary-sim-console 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the beekeeper for a simulated apiary running one full season. You manage the yard with the apiary console tools. This skill explains how to use the tools — deciding what each hive needs, where to put it, and when to pull honey is your job.
Your tools (mcp:apiary-sim/*)
Observe (read-only — gather information):
get_hives— the hives in the yard with a quick summary (boxes, population). Summary only.inspect_hive { hive }— open one hive for a detailed look: brood pattern, population, field-visible health signs. Also pulls a mite-wash sample.pest_pressure { hive }— the measured mite/pest reading for a hive. Needs a fresh sample first (inspect_hiveorschedule_inspection); otherwise it reports no sample. It tells you the treatment threshold.forage_map— the forage sources blooming this season, each with bloom status and nectar quality.weather_season— the week-by-week weather outlook.harvest_forecast— the projected honey-flow curve by week (relative nectar income). You read the curve.
Act (consequential):
schedule_inspection { hive, week }— book an inspection; this produces a fresh pest sample forpest_pressure.treat { hive, week, reason }— apply a treatment to a hive. Treating a colony that doesn't need it adds stress for little benefit.place_hive { hive, location }— place/move a hive at a forage location for the season.harvest { hive, week }— pull honey supers from a hive in a given week.close_season { notes }— end the season and submit for grading. This returns the graded result. Call it last.
How to run a season
- Survey the yard:
get_hives, theninspect_hivethe ones you want a closer look at. - To get a mite reading from
pest_pressure, sample first — viainspect_hiveorschedule_inspection. - Read
forage_map,weather_season, andharvest_forecastto understand this season's conditions. - Act:
treat,place_hive, andharvestas your judgment dictates. Each act takes aweekso timing is yours to set. close_seasononce when you are done — it grades colony health and harvest yield.
What ships with it
3 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.
- 2d ago First seen · 39 lines · 81 tokens per session scan A 75f90f262c73
apiary-sim-console is a skill published in the GitHub repository comisai/comis (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 81 tokens to every session and 765 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-08-31.
Other skills, from other repositories
org-sync
Use when the CEO wants an organization-wide sync across PuPu's agent teams — running each org's internal sync, then a cross-org sync where departments challenge each other, converging into one decision list. Triggers: "跑一次 org sync", "全局同步", "组织盘点", "/org-sync", "各部门现在什么情况", "有什么要我拍板的".
release-feature-audit
Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…
growth-analyst
Use when analyzing PuPu's open-source growth or health for the founder — GitHub traffic, downloads/installs, releases, community, or contributor activity — or when producing a growth report or weekly COO report. Repo is haoxiang-xu/PuPu. Triggers: "how is PuPu growing?", "are people installing PuPu?", "which release…
test-api
Use when running QA / regression tests against PuPu, when verifying a code change actually works in the running app, or when reading PuPu UI/state without screenshotting manually. Triggers on tasks like "test that PuPu still creates chats correctly", "verify the new model selector works end-to-end", "send a message…
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".