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.
git clone --depth 1 https://github.com/myclaude-sh/myclaude-creator-engineWrote 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/plugins/myclaude-sh/myclaude-creator-engine/studio-engine-core)<a href="https://agentmods.dev/plugins/myclaude-sh/myclaude-creator-engine/studio-engine-core"><img src="https://agentmods.dev/badge/plugins/myclaude-sh/myclaude-creator-engine/studio-engine-core/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/plugins/myclaude-sh/myclaude-creator-engine/studio-engine-core"><img src="https://agentmods.dev/badge/plugins/myclaude-sh/myclaude-creator-engine/studio-engine-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
studio-engine-core 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 1mo 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
{
"name": "studio-engine-core",
"description": "Core creation pipeline: onboard, create, fill, validate, test, package, publish — guided product creation with 20 structural quality patterns",
"skills": [
".claude/skills/onboard",
".claude/skills/create",
".claude/skills/fill",
".claude/skills/validate",
".claude/skills/test",
".claude/skills/package",
".claude/skills/publish",
".claude/skills/status",
".claude/skills/help"
],
"strict": false
}What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 418 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#studio-engine-core 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.
- 1mo ago First seen · 16 lines scan A 0bcd4f7aa385
studio-engine-core is a plugin published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
project-standards
Claude skill authoring standards, workspace management, and skills/tools registry lookup.
multica-ops
The layer around the official multica-cli skill — desktop-app binary discovery, the bridged Cowork/claude.ai route, shell and JSON shapes that bite, platform limits, and how to work a board governed by a repository that versions its Multica configuration.
gws
Operate across all Google Workspace services using the gws CLI — 100 skills, 15 slash commands, 11 role-based agents, and 44 automation recipes covering email, calendar, drive, docs, sheets, slides, tasks, chat, meet, forms, classroom, keep, people, events, admin reports, model armor, and apps script.
fakoli-state
Local-first, runtime-neutral project state for humans and AI coding agents — turn PRDs into lockable, evidence-backed work packets.