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 objectstack-ai/objectstack --skill objectstack-upgradegit clone --depth 1 https://github.com/objectstack-ai/objectstackWrote 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/objectstack-ai/objectstack/objectstack-upgrade)<a href="https://agentmods.dev/skills/objectstack-ai/objectstack/objectstack-upgrade"><img src="https://agentmods.dev/badge/skills/objectstack-ai/objectstack/objectstack-upgrade/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/objectstack-ai/objectstack/objectstack-upgrade"><img src="https://agentmods.dev/badge/skills/objectstack-ai/objectstack/objectstack-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00187 | $0.06028 |
| Opus 5.5 | $0.00075 | $0.02411 |
| Sonnet 5.5 | $0.00037 | $0.01206 |
| Haiku 4.5 | $0.00019 | $0.00603 |
Grade A, and why
objectstack-upgrade 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 today.
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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrading an ObjectStack metadata project across a protocol major
preflight → mechanical chain → semantic residue → acceptance report
⛔ The boundary — read this before the first command
Never hand-write a rewrite the chain already applies. If a key was renamed, the conversion table knows the rename; running the chain attributes each rewrite to a hop and proves the result is schema-valid. A hand-edit does neither, and it silently diverges the moment the chain gains an entry.
Never add a tolerant read to make old metadata load. No ?? alias, no
"accept both spellings" branch, no coercion in the project's own code. A key was
retired because nothing enforced it or because exactly one spelling survives;
re-admitting the old one at the consumer is how the defect the retirement closed
comes back inside the customer's repo, where no gate can see it.
Never resolve a residue item by guessing the owner's intent. The residue exists precisely because it is a business decision. The rule for when you decide alone and when you ask is in Layer 2 — it is the most important paragraph in this skill.
Never report "upgraded" without the acceptance artifacts. validate green
plus the report is the machine criterion. Absent either, the status is
in progress, whatever the diff looks like.
One conversionId per commit, where the project's review culture allows it.
The id is the commit's subject line and its justification.
Quickstart
# 0 · preflight — what major is this project on, what major is installed?
grep -rn "protocol" objectstack.config.ts package.json | head
node -p "require('@objectstack/spec/package.json').version"
# 1 · mechanical — replay the chain (writes only --out; --write also rewrites the sites it can prove)
os validate > .upgrade/validate-before.txt 2>&1 || true # the control, kept
os migrate meta --from 16 --step
os migrate meta --from 16 --json > .upgrade/migrate.json
os migrate meta --from 16 --out .upgrade/migrated.stack.json
# 2 · semantic residue — harvest the prescriptions, then work each item
node -e "console.log(require('fs').readFileSync(require.resolve('@objectstack/spec/package.json').replace('package.json','spec-changes.json'),'utf8'))" > .upgrade/spec-changes.json
# 3 · acceptance — all four, not three
os validate # green (compare against validate-before.txt)
tsc --noEmit # tombstones type the retired keys as `never`
os migrate meta --from 17 --json # `applied` must be [] (see §3.3)
# → write .upgrade/REPORT.md (template in §3.4)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed 9f505b887fcc
- 2d ago Changed · -1 lines ff9a80928e41
- 3d ago Changed 71fe94026c15
- 5d ago Changed 0e94f0e4fe63
- 8d ago Changed · +1 lines 31aafca2342c
- 9d ago Changed · -4 lines 7d889be3bd90
- 23d ago Changed · -112 lines 2a91a6a32097
- 1mo ago Changed · +5 lines 7899523d96fa
- 1mo ago Changed · -101 lines · -22 tokens per session 107cff709e45
- 1mo ago First seen · 697 lines · 209 tokens per session scan A 2f35e0ce23b5
objectstack-upgrade is a skill published in the GitHub repository objectstack-ai/objectstack (72 stars, last pushed today), licensed Apache-2.0. It adds 187 tokens to every session and 6,028 once invoked, about $0.0007 per session on Opus 5.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-30.
Other skills, from other repositories
ontotect
Systematic ontology engineering for designing, constructing, reviewing, repairing, optimizing, refactoring, validating, documenting, and governing ontologies, vocabularies, taxonomies, knowledge graphs, semantic models, and mappings. Use for RDF/RDFS, OWL 2, SKOS, SHACL, SPARQL, OBO, Turtle, JSON-LD, RDF/XML…
integrate
Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
mykg
Run mykg knowledge-graph commands inside Claude Code from one slash command /mykg. The user describes intent in natural language (extract, append, sync, resume, approve, walkthrough, parse-docs, fetch-web, query); the skill parses intent, builds the right mykg CLI command from the live --help output, confirms, runs…
exchange-recovery
A recovery workflow for Exchange servers, which are systems used for organisational email and calendars. It covers planning a restoration from backups, creating a recovery job, and checking whether the service works afterward.
demand-deliverability-assessment
Use when a user asks whether a product demand (an existing forecast or a new order) can be delivered on knowledge network supply942verify: locate the forecast, read the inventory metric, run the kitting / net-demand function, and, only after explicit user confirmation, raise the simulated replenishment action.
supplychain-hd
A knowledge guide for tracing a product supply process from demand estimates through suppliers.