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/work-autonomouslynpx skills add OdinMB/ops-workflow --skill work-autonomouslygit 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/work-autonomously)<a href="https://agentmods.dev/skills/odinmb/ops-workflow/work-autonomously"><img src="https://agentmods.dev/badge/skills/odinmb/ops-workflow/work-autonomously.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.00030 | $0.00686 |
| Opus 5 | $0.00015 | $0.00343 |
| Sonnet 5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
work-autonomously 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Conventions
Rules for commands and skills that run without user input (e.g., /ops:get-to-work, /ops:batch-execute). The goal is to keep moving and defer human judgment to a structured follow-up review.
Core Rules
- Never stop for user input. Record questions and move on.
- Never delete files. Record intended deletions in the follow-up file.
- Never push to remote. Only local branches and commits.
- When uncertain, make a sensible choice and move on. Record your reasoning and alternatives in the follow-up file so the user can review. Only skip when the wrong choice could have truly bad consequences (data loss, security, breaking external contracts). Getting work done with transparent doubts beats a slightly lower chance of mistakes.
Follow-Up File
Create a follow-up .md file in the project's plans directory (.plans/ or plans/, whichever the project uses) at the start of the process. It captures everything that needs human review afterward.
Required sections
## Controversial Decisions
Items where the agent made a judgment call the user should review.
## Skipped Items
Opportunities identified but not acted on, with reasons.
## User Input Needed
Questions that blocked progress on specific items.
## Files to Delete
Files that should be removed (agent does not delete files autonomously).
## Implementation Issues
Problems encountered during execution.
## Borderline Insights
Findings that might warrant persisting to the project's knowledge system (e.g., MEMORY.md, CLAUDE.md, or equivalent) but the agent wasn't confident enough to add directly. User should review and decide whether to keep or discard.
## Suggested Follow-Up Work
Potential new work items that emerged during execution but the agent wasn't confident enough to add directly (e.g., to a backlog, TODO list, or issue tracker). User should review and decide whether to act on or discard.
Not every section will be used by every command — include the ones that are relevant.
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.
- 3d ago First seen · 64 lines · 30 tokens per session scan A d97de5bc9f08
work-autonomously is a skill published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 16d ago), licensed MIT. It adds 30 tokens to every session and 686 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…
factory-api
API conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router composition, pagination shape, multi-field search via Drizzle ilike + or(), mutation lifecycle hooks, conditional query enabling, stale-time defaults, error response shape and…