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 find-my-bottlenecksgit 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/find-my-bottlenecks)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/find-my-bottlenecks"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/find-my-bottlenecks/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/find-my-bottlenecks"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/find-my-bottlenecks.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.00071 | $0.01393 |
| Opus 5 | $0.00036 | $0.00696 |
| Sonnet 5 | $0.00014 | $0.00279 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
find-my-bottlenecks 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find My Bottlenecks
When to use
- User asks "what's stuck," "what's blocking progress," "why aren't we moving on X."
- Most recent weekly review (from this agent) repeats risk or ask from prior one.
- Goal flipped to off-track and linked initiative also slipped.
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.
- Project tracker (Linear, Notion, Asana) - Optional. Surfaces stalled initiatives and ticket-level blockers; I work without it but with less signal.
- Team chat (Slack) - Optional. Lets me catch repeating asks across threads.
This skill works without any connection - it leans mostly on what's already in your saved work. 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.
- Active priorities - Required. Why I need it: a bottleneck only matters if it blocks something you're pushing on. If missing I ask: "What are the 2 to 3 things the company is pushing on this quarter?"
- Key contacts - Required. Why I need it: I propose owners to unblock; without contacts I'd be guessing names. If missing I ask: "Who unblocks what - engineering, sales, ops? Names plus how to reach them."
- Recent decisions, reviews, or goal snapshots - Optional. Why I need it: more saved work means stronger evidence. If you don't have it I keep going with TBD and lean on what's there.
Steps
-
Read
context/operations-context.md. If missing or empty, stop and ask user runset-up-my-ops-infofirst. Priorities and key-contacts anchor "proposed owner to unblock" logic. -
Gather evidence from last 4 weeks (handle each source as "if present, use it; if missing, continue"):
reviews/- last 4 weekly review files. Look for repeating risks / asks.triage/- last 4 inbox-triage files. Recurring "can-wait" threads from same person hint at delegation bottleneck.decisions.json- any decision withstatus: "pending"older than 14 days → decision-latency bottleneck.goal-history.json- any goal metricoff-trackacross two or more consecutive snapshots → bottleneck candidate tied to linked initiative.- this agent
anomalies.json- repeating open anomalies hint at data-or-process bottleneck.
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 · 91 lines · 71 tokens per session scan A 6ef57ef04a22
find-my-bottlenecks is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 71 tokens to every session and 1,393 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-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.