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 oomol-lab/skills --skill oo-agiledgit clone --depth 1 https://github.com/oomol-lab/skillsWrote 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/oomol-lab/skills/oo-agiled)<a href="https://agentmods.dev/skills/oomol-lab/skills/oo-agiled"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-agiled/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/oomol-lab/skills/oo-agiled"><img src="https://agentmods.dev/badge/skills/oomol-lab/skills/oo-agiled.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.00047 | $0.01025 |
| Opus 5.5 | $0.00019 | $0.00410 |
| Sonnet 5.5 | $0.00009 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade C, and why
oo-agiled scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux This is a copy
77% identical to oo-17track — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agiled
Operate Agiled through your OOMOL-connected account. This skill calls the agiled connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Running an action
Assume the user has already installed the oo CLI, signed in, and connected Agiled. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "agiled" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "agiled" --action "<action_name>" --data '<json>' --json
--datatakes a JSON object string or@path/to/file.json; omit it to send{}.- The response is
{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives undermeta.executionId.
Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.
Available actions
create_contact— Create an Agiled CRM contact. [write]create_project— Create an Agiled project. [write]create_task— Create an Agiled task. [write]delete_contact— Delete an Agiled CRM contact. [destructive]delete_project— Delete an Agiled project. [destructive]delete_task— Delete an Agiled task. [destructive]get_contact— Get one Agiled CRM contact by ID.get_project— Get one Agiled project by ID.get_task— Get one Agiled task by ID.list_contacts— List Agiled CRM contacts.list_projects— List Agiled projects.list_tasks— List Agiled tasks.update_contact— Update an Agiled CRM contact. [write]update_project— Update an Agiled project. [write]update_task— Update an Agiled task. [write]
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 Changed · -1 lines 13585c0564ec
- 1mo ago Changed · +1 lines e3f25dc37a9b
- 1mo ago First seen · 93 lines · 47 tokens per session scan C 8df547d73a0f
oo-agiled is a skill published in the GitHub repository oomol-lab/skills (2 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,025 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 77% identical to oo-17track, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
internal-comms
Author clear, high-impact internal engineering communications including 3P status updates, blameless incident postmortems, architecture decision memos, and leadership briefs. Use when writing technical updates, sprint reports, incident reviews, or organizational engineering announcements.
wrongstack-kanban
Record substantial project work on WrongStack's IPC-backed Kanban board so it survives the session and other agents can see it. Covers card detail, the managed Backlog→Todo→Running→Review→Done lifecycle, lease-fenced dispatch, and what "verified" means before a card reaches Done.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
stakeholder-alignment
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.