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/amusleh-spotware-com/terse-sharp/releasegit clone --depth 1 https://github.com/amusleh-spotware-com/terse-sharpWrote 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/amusleh-spotware-com/terse-sharp/release)<a href="https://agentmods.dev/commands/amusleh-spotware-com/terse-sharp/release"><img src="https://agentmods.dev/badge/commands/amusleh-spotware-com/terse-sharp/release.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.00048 | $0.03839 |
| Opus 5 | $0.00024 | $0.01920 |
| Sonnet 5 | $0.00010 | $0.00768 |
| Haiku 4.5 | $0.00005 | $0.00384 |
Grade A, and why
release scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://api.nuget.org/v3-flatcontainer/tersesharp/index.json How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚫 HARD GATE — a release is public the moment it is pushed. Every phase runs, in order.
nuget delete only unlists; a wrong answer shipped in a package costs every agent that installs
it. $ARGUMENTS — if it parses as X.Y.Z, that is the version; otherwise the version is derived
in R2. Nothing else takes input from the user.
Banned for the whole run:
AskUserQuestion,ExitPlanMode, "shall I tag now?", handing work back. Autonomous R0 → R9.- Tagging while a review is open, or with an unaddressed CRITICAL/WARNING. R3 is not optional and not satisfied by "a reviewer was spawned" — its report must exist and have been read.
- Tagging on a red anything: a red build, a red suite, a red
dotnet formatverify, a red CI run on the commit being tagged. "It passed on rerun" is not a diagnosis. - Re-tagging, moving or deleting a pushed tag. The tag is the identity of the build. A bad release is fixed forward with a new patch version, and the bad one is unlisted on nuget.org.
- Implementing a feature, fixing an unrelated bug, or refactoring. This command releases what is on
main. Only two content edits are in scope:CHANGELOG.md(R4) and a fix demanded by a red gate or a review finding (R3/R6). Anything else is scope creep — log it, do not do it. Read/Grep/Glob/Edit/Write, andBash: git status,git diff,grep,rg,cat,head,tail,sed,awk,ls,find,dotnet build,dotnet test. All terse-sharp calls. Only git history, index/history mutation (add,commit,tag,push),gh,dotnet tool install/update, the twodotnet formatverify commands (R2.5) and the NuGet probe stay onBash.- A blind wait. Every wait detects the run dying, not only the artifact appearing.
git add -A/git commit -am. Stage by path — this tree is shared with other sessions.- A
Co-Authored-By:trailer.
R0 — Preflight
- Invoke the
terse-sharpskill;workspace_status/load_workspace TerseSharp.slnx; passworkspace: "TerseSharp"on every call. Bash: git fetch origin --tags && git rev-parse --abbrev-ref HEAD. Must bemain; if not,git switch main.git pull --ff-only.changed_files. Uncommitted work is NOT released — the tag is cut onHEAD, and CI checks out the tag into a clean tree. List every dirty path in the R9 report as "not in this release", and never stage a path this run did not itself produce.Bash: git log --oneline $(git describe --tags --abbrev=0)..HEAD— the commits this release contains. If the range is empty, there is nothing to release: say so and stop after R9's report. That is the one legitimate early exit, and it is reported, not silent.TaskCreateone task per phase.
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.
- 4d ago First seen · 221 lines · 48 tokens per session scan A 0bde45be9d57
release is a command published in the GitHub repository amusleh-spotware-com/terse-sharp (2 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 3,839 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
rollback
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
ci
Trigger GitHub Actions CI/CD builds, sign, publish, or check CI status.
release
This document describes the standard release process for agtrace.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.