Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/gkrumbach07/openshell-dashboard/proto-sync)<a href="https://agentmods.dev/skills/gkrumbach07/openshell-dashboard/proto-sync"><img src="https://agentmods.dev/badge/skills/gkrumbach07/openshell-dashboard/proto-sync.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.1 | $0.00034 | $0.00414 |
| Opus 5 | $0.00017 | $0.00207 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
proto-sync 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.
What it actually says
SDK Sync
This repo no longer copies upstream proto files or regenerates local stubs. When OpenShell changes upstream, update the pinned Go SDK version and audit the affected handlers/models instead.
Note:
proto-syncremains only as a discoverable alias for older prompts. The live workflow is SDK-first per ADR 0003.
Steps
1. Inspect upstream changes
git -C ../OpenShell fetch upstream main
Then compare the pinned SDK version against upstream:
sdk/go/openshell/v1/for public client methods and resource shapessdk/go/openshell/v1/types/for request/response field detailssdk/go/proto/sandboxv1/only when the frontend policy protojson contract is involved
2. Bump the vendored SDK
cd backend
go get github.com/NVIDIA/OpenShell/sdk/go@<version-or-commit>
go mod tidy
3. Update call sites if the SDK shape changed
- Handlers should keep calling
app.sdk.<SubClient>()... - DTO shaping belongs in
backend/internal/models/sdk_converters.go - Policy JSON compatibility belongs in
backend/internal/models/policyproto.go - Only keep
backend/internal/sdkclient/rawexec.goif the public SDK still lacks non-TTY stdin exec
4. Check for new user-facing capabilities
Compare upstream capabilities with the dashboard surface to see whether we should expose anything new. Prefer the public SDK. If a feature is missing in the SDK, document the exact gap before adding any workaround.
5. Commit
git add backend/go.mod backend/go.sum
git commit -m "build: bump OpenShell Go SDK"
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 Changed · +5 lines · +1 tokens per session 535c391db2b2
- 5d ago First seen · 50 lines · 33 tokens per session scan A 0f09d4ecb048
proto-sync is a skill published in the GitHub repository Gkrumbach07/openshell-dashboard (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 414 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…