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 LiXin97/agora-lab --skill core-kanbangit clone --depth 1 https://github.com/LiXin97/agora-labWrote 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/lixin97/agora-lab/core-kanban)<a href="https://agentmods.dev/skills/lixin97/agora-lab/core-kanban"><img src="https://agentmods.dev/badge/skills/lixin97/agora-lab/core-kanban/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/lixin97/agora-lab/core-kanban"><img src="https://agentmods.dev/badge/skills/lixin97/agora-lab/core-kanban.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.00022 | $0.00208 |
| Opus 5 | $0.00011 | $0.00104 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
core-kanban 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 10d 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
Core Research Task Board
Use bash ../../scripts/lab-kanban.sh for all Research task board movement. Do not edit the Research task board file directly; use the canonical kanban path from your AGENTS/CLAUDE instructions.
Required State Discipline
- Read the task before starting.
- Move
Backlog -> In Progressonly when you are actively working on it. - Publish artifact paths when submitting for review.
- Do not treat
Doneas "I think it is fine." Treat it as "reviewed and accepted."
Required Inputs For Every Submission
- task ID
- artifact paths
- short summary of what changed
- any remaining risk or uncertainty
Escalate Instead Of Guessing
If the task definition is underspecified, use core-handoff to ask for clarification before inventing your own goal.
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.
- 10d ago First seen · 27 lines · 22 tokens per session scan A 52a7117122db
core-kanban is a skill published in the GitHub repository LiXin97/agora-lab (49 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 208 once invoked, about $0.0001 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-30.
Other skills, from other repositories
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
sprint-progress-report
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
ops-desk
Operate a project, workspace, or account from an agent or manager dashboard: inspect state, triage risks, prepare governed actions, route to the right skill lane, require approvals for consequential acts, and verify receipts after execution.
business-ops
Route one business signal through a replayable governed ops graph: classify, docs, release, work, outreach, spend, and proof, with consequential actions stopping at the right gate.