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 skills/objectstack-ai/claude-plugin/objectstacknpx skills add objectstack-ai/claude-plugin --skill objectstackgit clone --depth 1 https://github.com/objectstack-ai/claude-pluginWhat 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.00052 | $0.01246 |
| Opus 5 | $0.00026 | $0.00623 |
| Sonnet 5 | $0.00010 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
objectstack 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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ObjectStack
This skill connects you to an ObjectStack environment. An ObjectStack environment exposes its data objects (tables) and its business actions (registered app logic: approvals, conversions, flow triggers) as tools over the Model Context Protocol (MCP). Every operation runs as you — under your account's permissions and row-level security — so you may see a subset of rows, or get a permission error on a write. That is expected governance, not a failure.
When to use
Use these tools whenever the user wants to inspect or change data in their ObjectStack app — look up records, filter/report, create or update entries, clean up data — or run a business action the app defines (approve a request, convert a lead, kick off a flow). Prefer these tools over guessing — the environment is the source of truth, and an action is always better than hand-editing the records it would have touched.
Connect
This skill drives the MCP server at:
<YOUR_ENV_MCP_URL>
Two authentication tracks are supported:
OAuth (recommended for interactive clients). Add the URL as a remote MCP server with no credentials; the deployment is its own OAuth 2.1 authorization server, so an OAuth-capable client (claude.ai custom connectors, Claude Desktop, Claude Code) discovers it automatically, registers itself, and opens a browser login. You sign in as yourself and every tool call runs under your own permissions. Example (Claude Code):
claude mcp add --transport http objectstack <YOUR_ENV_MCP_URL>
API key (headless: CI, scripts, agents without a browser). Send an ObjectStack API key as a request header (the key is shown to you once when created; treat it like a password):
x-api-key: <YOUR_API_KEY>
(Authorization: ApiKey <YOUR_API_KEY> and Authorization: Bearer <YOUR_API_KEY> are also accepted.) If your MCP client supports custom
headers on a remote server, set the header there.
Discover before you act
The schema is not baked into this skill — it is discovered live, so it is always current even as the app evolves:
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.
- yesterday First seen · 117 lines · 52 tokens per session scan A ed114bef1dfa
objectstack is a skill published in the GitHub repository objectstack-ai/claude-plugin (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,246 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…