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 akiotanaka847/qaio-desktop --skill set-up-my-ops-infogit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/set-up-my-ops-info)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/set-up-my-ops-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-ops-info/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/akiotanaka847/qaio-desktop/set-up-my-ops-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-ops-info.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.00067 | $0.01464 |
| Opus 5 | $0.00034 | $0.00732 |
| Sonnet 5 | $0.00013 | $0.00293 |
| Haiku 4.5 | $0.00007 | $0.00146 |
Grade A, and why
set-up-my-ops-info 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 7d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up My Ops Info
This agent OWNS context/operations-context.md. No other agent writes it. This skill creates or updates it. Its existence unblocks this agent.
When to use
- "set up our operating context" / "draft the operating doc" / "document how we work".
- "update the operating context" / "priorities changed, fix the doc".
- Called implicitly by other skill needing context doc and finds missing - only after confirming with user.
Connections I need
I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Inbox (Gmail, Outlook) - Optional. Lets me sample sent messages so the voice section reflects how you actually write.
- Calendar (Google Calendar, Outlook) - Optional. Helps me infer your operating rhythm (deep-work days, meeting density).
- Files (Google Drive) - Optional. If you point me at an existing operating doc I read it before drafting.
This skill works without any connection - connections just make the doc richer. I never block here.
Information I need
I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- Company snapshot - Required. Why I need it: every other skill leans on what you make, who it's for, and your stage. If missing I ask: "In one or two sentences, what does the company make and who is it for? And where are you today - pre-launch, early users, scaling?"
- Active priorities - Required. Why I need it: every weekly review and approval flow keys off these. If missing I ask: "What are the 2 to 3 things the company is pushing on this quarter?"
- Operating rhythm - Required. Why I need it: shapes brief delivery, deep-work protection, meeting load. If missing I ask: "How do you like to work - deep-work days, meeting days, max meetings in a day, timezone?"
- Key contacts - Required. Why I need it: anchors VIP routing and "who unblocks what." If missing I ask: "Who are your key contacts - lead investor, closest advisor, anchor customers, fractional legal or finance?"
- Vendor posture - Required. Why I need it: drives tone for renewals and procurement. If missing I ask: "How do you approach vendors - conservative, balanced, or move fast? Who can sign? Annual or monthly?"
- Hard nos - Optional. Why I need it: stops me from drafting things you'd never send. If you don't have it I keep going with TBD using the workspace defaults.
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.
- 7d ago First seen · 77 lines · 67 tokens per session scan A d09b5e38d173
set-up-my-ops-info is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 67 tokens to every session and 1,464 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
env-setup-assistant
Expert guide for setting up development environments including IDE configuration, tooling, dependencies, and developer onboarding. Use when bootstrapping new projects or standardizing team environments.
meeting-processor
Process meeting transcripts and Notion meeting notes into structured organizational records, action items, and memory updates.
mailroom-acknowledgement-sweep
Route unrouted mail and chase what nobody acknowledged.
asset-inventory-reconciliation
Reconcile recorded against observed assets.
committed-schedule-coordination
Keep committed schedule and reality in step.