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.
/plugin marketplace add patchorbit/domscribenpx agentmods add plugins/patchorbit/domscribe/marketplacegit clone --depth 1 https://github.com/patchorbit/domscribeGrade A, and why
domscribe 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- domscribe — 89% identical, 64 lines differ
What it actually says
{
"name": "domscribe",
"owner": {
"name": "Patch Orbit",
"email": "[email protected]"
},
"metadata": {
"description": "Domscribe is a pixel-to-code development tool that maps running UI elements to their exact source locations, capturing runtime context (props, state, DOM) for handoff to coding agents via MCP."
},
"plugins": [
{
"name": "domscribe",
"description": "Domscribe is a pixel-to-code development tool that maps running UI elements to their exact source locations, capturing runtime context (props, state, DOM) for handoff to coding agents via MCP.",
"source": "./",
"homepage": "https://github.com/patchorbit/domscribe",
"repository": "https://github.com/patchorbit/domscribe",
"license": "MIT",
"keywords": [
"domscribe",
"pixel-to-code",
"ui-to-code",
"dom-annotation",
"annotation",
"source-mapping",
"runtime-context",
"element-inspector",
"component-inspector",
"mcp",
"model-context-protocol",
"developer-tools",
"devtools",
"react",
"vue",
"nextjs",
"nuxt"
]
}
]
}
What ships with it
1 file beside marketplace.json 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 · 40 lines scan A 6881b0fe0be2
domscribe is a plugin published in the GitHub repository patchorbit/domscribe (187 stars, last pushed 23d 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-08-30.
Other plugins, from other repositories
community
Plugin marketplace listing 1 plugin: nowledge-mem.
nowledge-mem-claude-code-plugin
Personal knowledge graph for Claude Code and Grok — remembers decisions, searches past work, captures sessions.
nowledge-mem-copilot-cli-plugin
Personal knowledge graph for GitHub Copilot CLI — remembers decisions, searches past work, captures sessions.
nowledge-mem-proma-plugin
Personal knowledge graph for Proma — saves Proma conversations, writes startup context into CLAUDE.md, and keeps nmem tools available during work.
proctor-marketplace
proctor: a guard that catches AI coding agents gaming their own test suites.
proctor
Catches AI coding agents gaming their test suites: deleting tests, skipping them, weakening assertions, or hardcoding outputs to fake a green build. Installs the honest-completion ruleset and a Stop hook that blocks a turn on any error-severity finding.