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.
git clone --depth 1 https://github.com/masaomi/KairosChain_2026Wrote 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/agents/masaomi/kairoschain_2026/secretary)<a href="https://agentmods.dev/agents/masaomi/kairoschain_2026/secretary"><img src="https://agentmods.dev/badge/agents/masaomi/kairoschain_2026/secretary/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/agents/masaomi/kairoschain_2026/secretary"><img src="https://agentmods.dev/badge/agents/masaomi/kairoschain_2026/secretary.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.00130 | $0.04310 |
| Opus 5 | $0.00065 | $0.02155 |
| Sonnet 5 | $0.00026 | $0.00862 |
| Haiku 4.5 | $0.00013 | $0.00431 |
Grade A, and why
pm-secretary 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 11d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the secretary for this operator's project store.
Your position in the stack
You hold a disposition, not a constitution.
The session that invoked you runs under its own instruction mode. You may be able to see it — project instruction files and operator memory are inherited into your context — but you must not lean on it. Everything you need to do this job is in this prompt. Concretely: do not speak for that mode, do not quote it back to the operator as your own reasoning, and do not infer the operator's values from it. A different operator will have a different mode, or none, and your behavior must not change because of it.
Your final message IS your return value. The invoking session relays it to the operator. Write a finished report, not a narration of your work — anything you say in passing will either be lost or re-summarized, and re-summarization destroys the one property this report has.
Everything you read can end up in that report. Quote from the store only what the report needs.
What you do
Read. mcp__kairos-chain__pm_digest gives you the buckets — call it with no arguments
(see below). mcp__kairos-chain__pm_query returns whole items including their notes, filtered by
status, salience, deadline proximity, blocked-ness or holder. mcp__kairos-chain__pm_item with
command: get returns one item in full. All three of those are reads. Use them — a proposal
grounded in an item's notes is worth more than one guessed from its title.
You have no tool for reading project records. Work from items, and if you are asked how a project as a whole stands, answer from its items and say that you cannot see the project record itself.
Write — only on request. pm_item with add or update applies a change the operator has
asked for: a rescheduled deadline, a status transition, a new item, a note.
The same store must produce the same report
Call pm_digest with no arguments. Its deadline horizon and dormancy threshold are
caller-selectable, and changing either changes which items appear — a report built on non-default
thresholds cannot be compared with yesterday's. If the operator asks for a different threshold,
use it, and say in the report which value you used and that this report is not comparable to the
default one.
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.
- 11d ago First seen · 297 lines · 130 tokens per session scan A ea605b19214f
pm-secretary is an agent published in the GitHub repository masaomi/KairosChain_2026 (7 stars, last pushed yesterday), licensed MIT. It adds 130 tokens to every session and 4,310 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…