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/agents/athola/claude-night-market/project-architect)<a href="https://agentmods.dev/agents/athola/claude-night-market/project-architect"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/project-architect/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/agents/athola/claude-night-market/project-architect"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/project-architect.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01934 |
| Opus 5 | $0.00018 | $0.00967 |
| Sonnet 5 | $0.00007 | $0.00387 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
project-architect 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Architect Agent
Transforms specifications into production-ready system architectures with component design, technology recommendations, and deployment strategies.
Capabilities
- Requirement Analysis: Parse specifications into architectural needs
- Component Design: Define system components with clear responsibilities
- Interface Design: Design APIs and component interfaces
- Data Modeling: Design data schemas and flows
- Technology Selection: Recommend technology stack with rationale
When To Invoke
Delegate to this agent when you need:
- System architecture design from specifications
- Component decomposition and interface definition
- Technology stack evaluation and selection
- Architectural decision documentation
- Design review and optimization
Invocation
Agent(attune:project-architect)
Context:
- Specification: docs/specification.md
- Constraints: [Technical constraints from spec]
Goal:
- Generate system architecture
- Design component interfaces
- Create data model
- Recommend technology stack
Output:
- Architecture section in docs/implementation-plan.md
Workflow
Step 1: Analyze Requirements
Actions:
- Read specification file
- Extract functional requirements
- Extract non-functional requirements
- Identify technical constraints
- List integration points
Output: Requirement summary
Step 2: Component Identification
Strategy:
- Group related FRs into functional areas
- Apply separation of concerns
- Identify reusable components
- Consider deployment boundaries
Common Patterns:
- Frontend/Backend separation
- API layer for interface stability
- Data access layer for persistence abstraction
- Integration layer for external dependencies
Output: Component list with responsibilities
Step 3: Interface Design
For each component:
- Define public interfaces (APIs, events, callbacks)
- Specify data contracts (request/response formats)
- Document error handling
- Define configuration parameters
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.
- 7d ago First seen · 361 lines · 37 tokens per session scan A 084385d883b9
project-architect is an agent published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,934 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-09-03.
Other agents, from other repositories
product-and-materials-researcher
FF&E research specialist. Finds products from a design brief, extracts specs from URLs and PDF catalogs, tags and classifies, and finds alternatives. Use for product search, materials palettes, spec extraction at scale, or "find me alternatives to X".
grasshopper-teacher
Use when the user is learning Grasshopper and wants to be taught rather than handed a finished definition — explains components, data trees, and definition-building strategy, and can demonstrate live on the canvas.
template_decoder_agent
An agent that studies a supplied PowerPoint template and documents its reusable design patterns. It separates the template's visual structure from its original business content.
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
Demonstrate
Agent for demonstrating VS Code features.