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/datathings/marketplace/upgradegit clone --depth 1 https://github.com/datathings/marketplaceWrote 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/datathings/marketplace/upgrade)<a href="https://agentmods.dev/commands/datathings/marketplace/upgrade"><img src="https://agentmods.dev/badge/commands/datathings/marketplace/upgrade.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.00025 | $0.03773 |
| Opus 5 | $0.00013 | $0.01886 |
| Sonnet 5 | $0.00005 | $0.00755 |
| Haiku 4.5 | $0.00003 | $0.00377 |
Grade C, and why
upgrade 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Dev**: stop server, `rm -rf gcdata`, replay importers. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://get.greycat.io/files/${path}/dev/latest" | cut -d'/' -f2 How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade GreyCat + Frontend
Purpose: Upgrade both ends' dependencies to latest, then lint + test both ends and fix every failure the upgrade surfaces until green:
- Backend — every
@libraryinproject.gclto latest from get.greycat.io. - Frontend — every
frontend/package.jsondependency to its latest published version (exact-pinned). - Verify + fix — backend
greycat lint+greycat test; frontendpnpm lint+vp build(+pnpm testif the project uses Vitest). Fix all lint/type/test failures the upgrade introduced in both back and front, re-running after each fix until everything passes.
Run When: Monthly maintenance, before major releases, on announced breaking changes.
Two tracks — parallelize under ultracode
The backend track (bump @library → greycat install → greycat fmt --mode=check + lint → greycat test → fix loop) and the frontend track (bump package.json → greycat codegen ts → pnpm lint → vp build/pnpm test → fix loop) are largely independent. Under ultracode/ultrathink, dispatch them as two parallel subagents (Task) and reconcile at the end; otherwise run sequentially.
Libraries
Core: std (required), explorer (dev UI).
Other published: ai, algebra, kafka, mqtt, opcua, ftp, ssh, osm, useragent, finance, powerflow, powergrid (successor to powerflow), text_search, fcs, and Pro-licensed ifc, sql, openid.
s3is not a library — S3 access is part ofstd(IO). Don't add@library("s3", ...). Resolve each library from its OWN endpoint — don't assume one shared version. The only name quirk:std's URL path iscore.
Backend Step 1: Resolve latest per lib
URL path-name = @library name, except std → core:
latest_version() { # $1 = @library name
local path="$1"; [ "$1" = "std" ] && path="core" # std's URL path is 'core'
curl -s "https://get.greycat.io/files/${path}/dev/latest" | cut -d'/' -f2
}
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 · 275 lines · 25 tokens per session scan C f17905d65c6f
upgrade is a command published in the GitHub repository datathings/marketplace (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 25 tokens to every session and 3,773 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.