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 loonghao/shotgrid-mcp-server --skill shotgrid-schema-discoverygit clone --depth 1 https://github.com/loonghao/shotgrid-mcp-serverWrote 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/loonghao/shotgrid-mcp-server/shotgrid-schema-discovery)<a href="https://agentmods.dev/skills/loonghao/shotgrid-mcp-server/shotgrid-schema-discovery"><img src="https://agentmods.dev/badge/skills/loonghao/shotgrid-mcp-server/shotgrid-schema-discovery/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/loonghao/shotgrid-mcp-server/shotgrid-schema-discovery"><img src="https://agentmods.dev/badge/skills/loonghao/shotgrid-mcp-server/shotgrid-schema-discovery.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00531 |
| Opus 5.5 | $0.00016 | $0.00212 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
shotgrid-schema-discovery 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 2d 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.
What it actually says
Discovering the ShotGrid schema
Read references/entity-types.md for the common entity types and the fields
worth asking for first.
Prefer resources over tools
This server exposes the schema as MCP resources alongside its tools. Resources are context loaded once, not a round trip per question:
| Resource | Contents |
|---|---|
shotgrid://schema/entities |
Every entity type, as sg.schema_read() returns it |
shotgrid://schema/statuses |
status_list fields of every entity type |
shotgrid://schema/statuses/{entity_type} |
status_list fields of one entity type |
Use the matching tool when you need a narrower or live answer:
| Goal | Tool |
|---|---|
| Fields of one entity type | schema_get |
| All entity types | sg_schema_entity_read |
| One field's schema | sg_schema_field_read |
Procedure
- Start with
shotgrid://schema/statuses/{entity_type}when the task involves status. It returns the valid codes and their display labels in one read, which is exactly what an update needs. - Use
schema_getfor field-level questions on a single entity type — data types, whether a field is required, whether it is editable. - Verify every field name before writing. Custom fields are named
sg_<something>and are studio-specific. A field that exists in one project may not exist in another. - Cache what you learned for the session. Schema rarely changes inside one task; do not re-read it between steps.
Pitfalls
- Do not assume a field exists because it exists on a similar entity type.
sg_status_listis common but not universal. - Entity type names are case-sensitive and capitalised (
Shot, notshot). - Custom entities are
CustomEntity01…CustomEntityNN; their human names live in the schema, not in the type name. - A schema read is not a data read. The schema tells you what a field is called, never what it currently holds.
What ships with it
1 file 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.
- 2d ago First seen · 55 lines · 39 tokens per session scan A 29509f3a50fb
shotgrid-schema-discovery is a skill published in the GitHub repository loonghao/shotgrid-mcp-server (65 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 531 once invoked, about $0.0002 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-09-23.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.