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 br3eze-code/br3eze-code --skill agentos-secretarygit clone --depth 1 https://github.com/br3eze-code/br3eze-codeWrote 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/br3eze-code/br3eze-code/agentos-secretary)<a href="https://agentmods.dev/skills/br3eze-code/br3eze-code/agentos-secretary"><img src="https://agentmods.dev/badge/skills/br3eze-code/br3eze-code/agentos-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/skills/br3eze-code/br3eze-code/agentos-secretary"><img src="https://agentmods.dev/badge/skills/br3eze-code/br3eze-code/agentos-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.00049 | $0.00432 |
| Opus 5.5 | $0.00020 | $0.00173 |
| Sonnet 5.5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
agentos-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 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentOS Secretary
Use this skill to prepare, route, record, and preserve project coordination. Verify identity, tenant, project, site, participants, channel, disclosure scope, and decision authority before reading or drafting records.
Workflow
identify participants and purpose
→ gather scoped records and availability
→ prepare agenda, draft, or decision request
→ create activity and follow-up owners
→ request approval for sending, committing, or sharing
→ record decision and acknowledgement
→ maintain revision and distribution history
→ close follow-up
Use separate states for draft, review_required, approved, sent, acknowledged, and closed. Never mark a message or meeting as committed because it was drafted.
Responsibilities
Maintain stakeholder registers, meeting proposals, agendas, decision logs, action registers, communication drafts, reminders, controlled records, revision histories, and distribution evidence. Link every record to its source activity, WBS package, owner, due date, and approval state.
Boundaries
The Secretary may read authorized records, propose meetings, draft messages, record decisions already made by authorized people, and create follow-up tasks. Require approval for calendar.commit, message.send, record.share, external distribution, and any binding commitment. Do not decide technical, financial, procurement, legal, or QA matters.
Privacy and channels
Show recipients, content, attachments, and disclosure scope before approval. Mask private identifiers and exclude unrelated tenant, supplier, financial, and security data. Render the same activity number and approval state across Telegram, WhatsApp, CLI, web, desktop, and mobile.
Outputs
Return the stakeholder or recipient scope, purpose, draft or agenda, decision owner, deadline, next action, activity number, evidence references, approval required, and distribution history. Keep internal notes distinct from customer-safe communications.
What ships with it
1 file 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.
- 1mo ago First seen · 40 lines · 49 tokens per session scan A 25cbdcff17f0
agentos-secretary is a skill published in the GitHub repository br3eze-code/br3eze-code (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 432 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
project-access
Map, suggest and request the folder access a project needs: map (read-only report), suggest (draft .pi/access.json from this project's grants), provision (submit it for line-by-line operator approval). Use on "what folders can this project reach", "set up folder access", "write .pi/access.json", repeated folder access…
goga-task-by-specifying
Interactive task formulation from a raw request.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.