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/attune)<a href="https://agentmods.dev/plugins/athola/claude-night-market/attune"><img src="https://agentmods.dev/badge/plugins/athola/claude-night-market/attune.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
attune 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": "attune",
"version": "1.9.19",
"description": "Full-cycle project development - brainstorm ideas, create specifications, plan architecture, initialize projects, and execute implementation with integrated workflows from superpowers and spec-kit",
"commands": [
"./commands/arch-init.md",
"./commands/blueprint.md",
"./commands/brainstorm.md",
"./commands/execute.md",
"./commands/mission.md",
"./commands/project-init.md",
"./commands/skill-library.md",
"./commands/specify.md",
"./commands/upgrade-project.md",
"./commands/validate.md",
"./commands/war-room.md"
],
"skills": [
"./skills/architecture-aware-init",
"./skills/dorodango",
"./skills/makefile-generation",
"./skills/precommit-setup",
"./skills/project-brainstorming",
"./skills/project-execution",
"./skills/project-init",
"./skills/project-planning",
"./skills/project-specification",
"./skills/war-room",
"./skills/war-room-checkpoint",
"./skills/workflow-setup",
"./skills/mission-orchestrator",
"./skills/skill-library-mission"
],
"agents": [
"./agents/project-architect.md",
"./agents/project-implementer.md"
],
"keywords": [
"full-cycle",
"brainstorm-plan-execute",
"spec-driven-development",
"project-initialization",
"brainstorming",
"specification",
"planning",
"implementation",
"execution",
"tdd",
"architecture",
"initialization",
"setup",
"automation",
"git",
"github-actions",
"pre-commit",
"makefile",
"python",
"rust",
"typescript",
"mission",
"orchestrator",
"lifecycle",
"templates",
"scaffolding",
"project-structure",
"best-practices",
"ci-cd",
"superpowers-integration",
"spec-kit-integration"
],
"author": {
"name": "Alex Thola",
"url": "https://github.com/athola"
},
"license": "MIT",
"dependencies": ["leyline", "abstract"]
}
What it installs
The manifest is a name and a version. 14 skills, 11 commands, 2 agents travel with it, and installing the plugin installs all of them — 757 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill mission-orchestrator A 36 tokens
- Skill project-brainstorming A 30 tokens
- Skill project-execution A 31 tokens
- Skill war-room A 35 tokens
- Skill war-room-checkpoint A 30 tokens
- Skill architecture-aware-init A 28 tokens
- Skill workflow-setup A 37 tokens
- Skill makefile-generation A 31 tokens
- Skill project-init A 40 tokens
- Skill project-planning A 28 tokens
- Skill dorodango A 31 tokens
- Skill project-specification A 25 tokens
- Skill precommit-setup A 39 tokens
- Skill skill-library-mission B 40 tokens
- Command blueprint A 21 tokens
- Command execute A 12 tokens
- Command specify A 15 tokens
- Command war-room A 26 tokens
- Command brainstorm A 22 tokens
- Command arch-init A 20 tokens
- Command mission A 16 tokens
- Command upgrade-project A 15 tokens
- Command validate A 14 tokens
- Command skill-library A 32 tokens
- Command project-init C 28 tokens
- Agent project-implementer A 38 tokens
- Agent project-architect A 37 tokens
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 · 78 lines scan A 655f5987190b
attune is a plugin published in the GitHub repository athola/claude-night-market (335 stars, last pushed yesterday), 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
analyze-issue
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
n8n-workflow-builder
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- \n Context: User wants to create a Slack notification workflow when a new GitHub issue i.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
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"…