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 agentmods add skills/odinmb/ops-workflow/find-oppsnpx skills add OdinMB/ops-workflow --skill find-oppsgit clone --depth 1 https://github.com/OdinMB/ops-workflowWrote 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/odinmb/ops-workflow/find-opps)<a href="https://agentmods.dev/skills/odinmb/ops-workflow/find-opps"><img src="https://agentmods.dev/badge/skills/odinmb/ops-workflow/find-opps.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01311 |
| Opus 5 | $0.00018 | $0.00656 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
find-opps 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Opportunities
Identify new directions of work the project should explore — things that aren't already tracked, aren't obvious from the existing backlog, and that the project owner may not have thought to pursue yet. The output is backlog-ready items — this skill does NOT execute them.
This is the outward-looking complement to /find-tasks, which finds work within existing paths. This skill looks beyond current plans to find new territory.
When to Use
- When
/find-taskslenses 1-6 yield fewer than 2 new items (existing paths are well-mined) - When the user asks "what else should we be thinking about?"
- Between major milestones when strategy should be reassessed
- When the project feels stuck or stale
Context Required
Before running this skill, you need the project overview already loaded (MEMORY.md, state files, backlog, recent plans, references). If you don't have it, gather it now:
MEMORY.md— project overview, goals, and knowledge mapstate/INDEX.md→ then every file listed in itbacklog/INDEX.md→ then every file and subfolder listed in itplans/INDEX.md→ then every active plan (not completed)plans/completed/INDEX.md— scan the 5 most recent completed plansreferences/INDEX.md— scan for existing research to avoid duplicating
Isolate the heavy reading when you're on an expensive model. If you're running on a frontier model (spawned from /find-all or /get-to-work, or a frontier interactive session), push the context-load above and the lens-3/lens-4 web research to a read-only reader subagent that returns a distilled overview + web digest with citations — then do the ideation (lenses, Filter, Constraints) yourself on that brief. Reading state files and full web pages doesn't need frontier judgment; the ideation does. Enumerate what the reader should extract, or it drops the signal. Skip this on a small project where there's nothing to isolate.
Analysis Lenses
Think laterally, but stay grounded. Every suggestion must be something an autonomous agent can actually start (research, analysis, drafting, knowledge management). The project's goals and constraints in MEMORY.md are your guardrails — stretch beyond current plans, not beyond what's realistic for this project.
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.
- 5d ago First seen · 98 lines · 37 tokens per session scan A 299fafe2dba8
find-opps is a skill published in the GitHub repository OdinMB/ops-workflow (6 stars, last pushed 18d ago), licensed MIT. It adds 37 tokens to every session and 1,311 once invoked, about $0.0002 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 skills, from other repositories
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-full-auto
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
factory-db-migration
The operational discipline for running a destructive change against a production database — schema migrations, data backfills, one-shot RPCs, historical seed imports. Adjacent to factory-data-layer.md (schema design) and factory-deployment.md (where migrations execute in CI) — this skill is about the runbook around…
people-intel
This skill should be used when the user asks to 'research person', 'person intel', 'people intel', 'who is [person]', 'who created [project]', 'who maintains [package]', 'add person to knowledge graph', 'enrich person note', 'update person note', 'document [person]', 'create person note for [name]'. Researches a…
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
dev-cycle
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.