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 commands/glassity/agent-skills/finops-executegit clone --depth 1 https://github.com/glassity/agent-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/commands/glassity/agent-skills/finops-execute)<a href="https://agentmods.dev/commands/glassity/agent-skills/finops-execute"><img src="https://agentmods.dev/badge/commands/glassity/agent-skills/finops-execute.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.00062 | $0.01722 |
| Opus 5 | $0.00031 | $0.00861 |
| Sonnet 5 | $0.00012 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
finops-execute 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/finops-execute — step 4: Execution
The automation dial and the level prompt live in the
glassity-five-stepsskill. Both are summarized below.
Purpose
Turn a Definition-of-Ready plan into a deployed, verified change. Friction
is the dominant variable, so the command meets the team where it is by running
at one of four automation levels, chosen per opportunity because risk
differs idea to idea. Apply the verification gate: the change is deployed,
its effect verified, and the rollback proven, before /finops-feedback can
close the loop.
Every write goes through the binary's two-phase confirmation.
Variables
| Variable | Source | Default | Meaning |
|---|---|---|---|
TARGET |
first positional arg | required | The assignment id to execute, or an opportunity id when run at opportunity scope. |
LEVEL |
asked per opportunity | none | L1, L2, L3, or L4. No default and no global flag — the human chooses each time. |
Tool surface
- CLI:
glassity --output=json opp show-assignment <id>oropp show <id>to re-read state,opp transitionandopp register-assignment-artifactto record the change,pr registerto record a pull request. At close, thelifecycle-mark-pr-mergedskill, whose transition the server accepts only once it has verified the merge. - L2:
Write, to generate an infrastructure diff or script the human runs. - L3:
gitandgh, to branch, apply the change, and open a pull request. git logsupplies the commit sha that artifact registration pins, at every level.- Binary check: run
command -v glassitybefore the first CLI call. If it is missing, stop and tell the user to install it withbrew install glassity/tap/glassityor from https://github.com/glassity/cli/releases. No account yet? Sign up at app.glassity.cloud.
Instructions
- First action: ask which automation level. Never assume one. Present the four choices with a recommendation keyed to the idea type:
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 · 139 lines · 62 tokens per session scan A 71985a18e8cd
finops-execute is a command published in the GitHub repository glassity/agent-skills (2 stars, last pushed 21d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,722 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-08-31.
Other commands, from other repositories
context
Hand a coding agent (or yourself) a slim, token-budgeted structural slice for a query — the relevant symbols, where they live, what calls them, and the module they belong to — read from the code graph at .dxkit/reports/graph.json. The point is to navigate by graph instead of repeated whole-file reads: the same…
brainstorm
Enhanced brainstorming with smart detection, design modes, time budgets, context-aware questions, and spec capture.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.