investor-update

investor-update is a command for Claude Code from navraj007in/architecture-cowork-plugin. It costs 11 tokens per session (1,982 once invoked), scanned A, original, Apache-2.0.

A command that creates an investor or stakeholder progress-update template from project files. Stakeholders are people who need regular updates, such as investors, clients, or internal managers.

In plain words
What is it for?
Preparing monthly investor updates, agency client reports, or internal project briefings using the project's architecture and scope data.
Why use it?
It gathers shipped features, technical decisions, costs, risks, and next steps from scattered project information. This reduces the manual work of assembling a progress report.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the architect plugin — 48 skills, 63 commands, 19 agents, 7 MCP servers shipped together

Good fit Preparing monthly investor updates, agency client reports, or internal project briefings using the project's architecture and scope data.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/navraj007in/architecture-cowork-plugin/investor-update
Install

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.

Clone the repo
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

Wrote 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.

agentmods badge for investor-update

README.md
[![agentmods](https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/investor-update/github.svg)](https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/investor-update)
Your own site
<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/investor-update"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/investor-update/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.

agentmods 80×15 button for investor-update

Your own site · 80×15
<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/investor-update"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/investor-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01982
Opus 5 $0.00005 $0.00991
Sonnet 5 $0.00002 $0.00396
Haiku 4.5 $0.00001 $0.00198

Measured 12d ago against content hash 16998e5362de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

investor-update 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 12d 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.

commands/investor-update.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/architect:investor-update

Trigger

/architect:investor-update — run at any time to generate a progress report.

Purpose

Generate a professional investor or stakeholder update template, pre-filled with real project data: features shipped, architecture decisions made, infrastructure costs, technical progress, and next priorities. Suitable for monthly investor updates, agency client reports, or internal stakeholder briefings. Saves hours of assembling progress from scattered sources.

Workflow

Step 1: Gather Project Data

Read in this order:

  1. architecture-output/_state.json — read first if it exists; provides compact project (name, description, stage), tech_stack (components and integrations), mvp_scope (must_have / wont_have), and top_risks (top 5 risks with scores and levels). Use these directly for sections 1, 3, 4, and 6 without reading full markdown files.
  2. SDL fileonly if _state.json is absent or lacks project/tech_stack; check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files. Read only the solution and architecture.projects sections (Grep for these) to get project name, description, stage, and component list.

If both _state.json and an SDL file are absent: "I need a project blueprint to write a stakeholder update from. Run /architect:blueprint first, then come back here."

  1. Cost estimatearchitecture-output/cost-estimate.md (if exists, typically small) — monthly infra costs
  2. Scaffold report.archon/scaffold-report.json (if exists) — component build status, timestamps
  3. Change requests.archon/change-requests/cr-index.json (if exists) — applied CRs with dates
  4. ADR files — any adr-*.md files in architecture-output/ — architecture decisions
  5. Security scanarchitecture-output/security-scan.md (if exists) — security posture; only if _state.json.top_risks is absent
  6. Complexity checkarchitecture-output/complexity-check.md (if exists) — risk assessment; only if _state.json.top_risks is absent
  7. Well-architected reviewarchitecture-output/well-architected-review.md (if exists)
  8. Hiring briefarchitecture-output/hiring-brief.md (if exists) — team needs
  9. Blueprintarchitecture-output/executive-summary.md (if exists) — project overview; only if _state.json is absent

Read the full file on GitHub · 199 lines

Changes

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.

  1. 12d ago First seen · 199 lines · 11 tokens per session scan A 16998e5362de

Subscribe to this mod's changes

investor-update is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,982 once invoked, about $0.0001 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-08-31.