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/athola/claude-night-marketWrote 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/athola/claude-night-market/imbue)<a href="https://agentmods.dev/plugins/athola/claude-night-market/imbue"><img src="https://agentmods.dev/badge/plugins/athola/claude-night-market/imbue.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
imbue 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 4d 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": "imbue",
"version": "1.9.19",
"description": "Intelligent workflow methodologies: analysis, evidence gathering, structured output, and research-enriched feature review with RICE/WSJF/Kano scoring",
"skills": [
"./skills/assisted-mastery",
"./skills/catchup",
"./skills/dependency-verification",
"./skills/diff-analysis",
"./skills/feature-review",
"./skills/graduated-implementation",
"./skills/latent-space-engineering",
"./skills/proof-of-work",
"./skills/review-core",
"./skills/rigorous-reasoning",
"./skills/scope-guard",
"./skills/structured-output",
"./skills/workflow-monitor",
"./skills/justify",
"./skills/vow-enforcement",
"./skills/karpathy-principles"
],
"commands": [
"./commands/catchup.md",
"./commands/justify.md",
"./commands/stewardship-health.md",
"./commands/structured-review.md",
"./commands/karpathy-check.md"
],
"agents": [
"./agents/review-analyst.md"
],
"hooks": [],
"keywords": [
"workflow",
"analysis",
"evidence",
"structured-output",
"methodology",
"review",
"catchup",
"scope-guard",
"anti-overengineering",
"feature-review",
"prioritization",
"RICE",
"WSJF",
"roadmap",
"research-enrichment",
"workflow-monitor",
"error-detection",
"karpathy",
"coding-pitfalls",
"discipline"
],
"author": {
"name": "Alex Thola",
"url": "https://github.com/athola"
},
"license": "MIT",
"dependencies": [
"leyline"
],
"optional_dependencies": [
"tome"
]
}
What it installs
The manifest is a name and a version. 5 commands, 1 agent travel with it, and installing the plugin installs all of them — 177 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 plugin.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.
- 4d ago First seen · 68 lines scan A b192439d6904
imbue is a plugin published in the GitHub repository athola/claude-night-market (335 stars, last pushed 2d 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
code-architect
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
sprint-prioritizer
Use this agent when planning 6-day development cycles, prioritizing features, managing product roadmaps, or making trade-off decisions. This agent specializes in maximizing value delivery within tight timelines. Examples:\n\n \nContext: Planning the next sprint\nuser: "We have 50 feature requests but only 6 day.
prd-specialist
Use this agent when you need to create comprehensive Product Requirements Documents (PRDs) that combine business strategy, technical architecture, and user research. Examples: Context: The user needs to create a PRD for a new feature or product launch. user: "I need to create a PRD for our new user authenticat.
planning-prd-agent
'MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature"…
pricing-packaging-specialist
Use this agent when you need to optimize B2B pricing strategies, packaging models, and revenue optimization for enterprise sales. This agent specializes in value-based pricing, usage-based billing, enterprise contract negotiations, and competitive pricing analysis for SaaS platforms. Examples.