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 agents/bitovi/convey/launch-angular-envgit clone --depth 1 https://github.com/bitovi/conveyWhat 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.00051 | $0.00672 |
| Opus 5 | $0.00026 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
launch-angular-env 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a dev-environment launcher for testing the Convey MCP inspector against the Angular 21 test app with Storybook support.
Goal
Set up the development environment so the MCP server (port 3335) serves the Angular test app on port 5177, with overlay and panel watchers rebuilding on every save, plus Storybook running on port 6009.
All commands run from the repository root unless otherwise noted.
Workflow
Step 1 — Kill conflicting processes
Kill any processes on ports 3335, 5177, and 6009:
lsof -ti :3335 | xargs kill -9 2>/dev/null || true
lsof -ti :5177 | xargs kill -9 2>/dev/null || true
lsof -ti :6009 | xargs lsof -ti :6009 | xargs lsof -ti :6009 | xargs lsof -ti :6009 | xargs lsof -ti :6009 | xarge compound task which starts all watchers and servers in parallel:
```bash
run_task("Dev: Angular")
This starts:
- Watch: Overlay (esbuild watcher)
- Watch: Panel (vite watcher)
- Watch: Angular CSS (Tailwind watcher)
- Server Angular (port 3335)
- Test App Angular (port 5177)
Step 3 — Run the Storybook Angular task
Start Storybook separately to ensure it runs without blocking other services:
run_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trup prints "Lrun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trun_trok started"
### Step 5 — Tell the user everything is ready
Report:
> ✓ Environment running:
> - Overlay watcher (rebuilds on save)
> - Panel watcher (rebuilds on save)
> - Angular CSS watcher (Tailwind)
> - Server on http://localhost:3335
> - Angular app on http://localhost:5177
> - Storybook on http://localhost:6009
>
> Open http://localhost:5177 to start testing with the overlay and inspector panel.
## Rules
- If any step fails, stop and report the error — do not continue.
- Always start the server from `test-app-angular/` so it resolves the correct `tailwindcss` package.
- The Angular server uses port 3335 (not 3333) to avoid conflicting with the React test app server.
- Storybook on port 6009 is part of the standard Angular dev environment.
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.
- 2d ago First seen · 65 lines · 51 tokens per session scan A e6d534742239
launch-angular-env is an agent published in the GitHub repository bitovi/convey (46 stars, last pushed 16d ago), licensed MIT. It adds 51 tokens to every session and 672 once invoked, about $0.0003 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-30.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
architecture
🇷🇺 Russian version: architecture.ru.md.