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.
npx agentmods add commands/philngt/contextd/business-viewgit clone --depth 1 https://github.com/philngt/contextdWrote 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/commands/philngt/contextd/business-view)<a href="https://agentmods.dev/commands/philngt/contextd/business-view"><img src="https://agentmods.dev/badge/commands/philngt/contextd/business-view.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01538 |
| Opus 5 | $0.00000 | $0.00769 |
| Sonnet 5 | $0.00000 | $0.00308 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
business-view 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business View
Dịch một artifact kỹ thuật (service, contract, pattern, ADR) sang business view — góc nhìn không-jargon, dành cho PM / business / executive đọc.
Output là tài liệu giải thích, KHÔNG sửa file gốc. Output ghi vào
{ws}/product/views/để tracking. Reference: pack-product retrieval-map, pack-product coding-rules.md (Translation table).
Input
| Arg | Required | Notes |
|---|---|---|
{target} |
required | Đường dẫn relative tới {ws}/ hoặc tên service/contract/pattern. Vd: projects/billing/services/invoice-service.md, platform/contracts/payment-api.md, hoặc invoice-service. |
--audience {who} |
optional | pm (default) / executive / customer-success / sales. Ảnh hưởng tone + depth. |
--out {path} |
optional | Override output. Default: {ws}/product/views/{slug-of-target}-business-view.md. |
Bước 0 — Workspace & pack check
- Resolve workspace. Set
{ws}. - STOP nếu workspace chưa init.
- Warn nhẹ nếu
pack-productchưa bật (command vẫn chạy, nhưng output không được pack-product validator check).
Bước 1 — Resolve target
- Nếu
{target}là path → check tồn tại trong{ws}/. STOP nếu không. - Nếu là tên (vd
invoice-service) → glob trong{ws}/:{ws}/projects/*/services/{target}.md{ws}/platform/contracts/{target}.md{ws}/platform/patterns/{target}.md
- Nhiều match → AskUserQuestion để user chọn.
- Set
target_path,target_type(service / contract / pattern / adr / unknown).
Bước 2 — Gather context (priority order)
Theo retrieval-map cross-pack section:
- Đọc
target_path— extract: name, purpose (1-line từ H1/intro), responsibilities (bullets), dependencies (other services/contracts). - Tìm related domain rules:
- Glob
{ws}/domains/*/workflow.md— nếu mentiontarget_name→ include.
- Glob
- Tìm related personas:
- Glob
{ws}/product/personas/*.md— nếu domain workflow của target chạm persona, include.
- Glob
- Tìm related briefs:
- Glob
{ws}/product/briefs/*.md— nếu frontmatter mentiontarget_namehoặc body link tớitarget_path→ include.
- Glob
- Tìm related metrics:
- Read
{ws}/product/metrics.md— nếu metric có dashboard liên quan target → include.
- Read
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 · 161 lines · 0 tokens per session scan A c92f4bc392a5
business-view is a command published in the GitHub repository philngt/contextd (29 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,538 tokens. 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 commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
orchestrate-brain
Weekly 30-minute second-brain review ritual. Orchestrates inbox clear, lightweight distillation, vault maintenance, cross-reference pass, and next-week capture focus. The compounding rhythm that keeps the system alive.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.