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 skills/nguyenvanphituoc/shapeup-sdlc-plugin/orientnpx skills add nguyenvanphituoc/shapeup-sdlc-plugin --skill orientgit clone --depth 1 https://github.com/nguyenvanphituoc/shapeup-sdlc-pluginWrote 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/skills/nguyenvanphituoc/shapeup-sdlc-plugin/orient)<a href="https://agentmods.dev/skills/nguyenvanphituoc/shapeup-sdlc-plugin/orient"><img src="https://agentmods.dev/badge/skills/nguyenvanphituoc/shapeup-sdlc-plugin/orient.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.1 | $0.00148 | $0.03638 |
| Opus 5 | $0.00074 | $0.01819 |
| Sonnet 5 | $0.00030 | $0.00728 |
| Haiku 4.5 | $0.00015 | $0.00364 |
Grade A, and why
orient 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 6d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orient — the Scout (Shape Up step 7)
In Shape Up, the team that builds also orients: after kick-off they read the real code,
spike the scary parts, and let reality generate Discovered tasks — which outnumber the
imagined ones. This skill is that pass, made explicit. It exists because the orchestrator
(tech-lead) must delegate orientation, and the generator (task-executor) can't host it:
its first gate needs a task file, and at Orient time no board exists yet — the board is
mapped after this pass, by ba-pitch-analyzer at step 8.
So the Scout's whole job is to make the planner's board reality-born instead of imagined.
It hands ba a map of where the pitch lands in real code, the findings from de-risking the
single scariest area, and a seed list of tasks (imagined + already-discovered). Nothing more.
PO: shaping → bet → kick-off ──► tech-lead ──► ORIENT (you) ──► ba (Map Scopes) ──► build
reads code, spikes, seeds
What the Scout is and is not
| Does | Does NOT |
|---|---|
| Read the kicked-off pitch + breadboard | Re-shape, re-bet, or question the appetite (PO already did) |
| Trace pitch elements to real files/modules | Write production code |
| Spike the single riskiest area, time-boxed | Build the scope board / tasks (that is ba, step 8) |
| Seed the discovered-task list (imagined + discovered) | Keep run-state (tech-lead owns it) |
| Emit raw hill signal (per-area unknowns) | Render the hill report (tech-lead renders it) |
The Scout is a pure worker (the harness rule: stateless workers, one stateful
orchestrator). It receives run metadata — feature, spec folder, stack — as arguments
from tech-lead; it never reads or writes a shared run-state file.
Input contract (pure worker)
Orchestrated, you are invoked as --order <path> (a WorkOrder): payload.pitch (the
kicked-off pitch path), payload.stack (sweep hint), payload.spec_folder (the SHARED spec
deliverable dir) and payload.feature (the run slug), plus substrate.allowed naming your one
write surface — the orient output dir. Anything absent = unknown: confirm at GATE O-A
(standalone) or report it in the result's deviations, never guess. Standalone, the
--pitch/--spec/--stack flags below carry the same fields; the output dir derives from the
spec path (.shapeup/<feat>/orient/).
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.
- 6d ago First seen · 264 lines · 148 tokens per session scan A 00b0b7fde1a9
orient is a skill published in the GitHub repository nguyenvanphituoc/shapeup-sdlc-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session and 3,638 once invoked, about $0.0007 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.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.