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/engindemirog/ai-native-engineering-workspaceWrote 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/engindemirog/ai-native-engineering-workspace/change)<a href="https://agentmods.dev/commands/engindemirog/ai-native-engineering-workspace/change"><img src="https://agentmods.dev/badge/commands/engindemirog/ai-native-engineering-workspace/change/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/commands/engindemirog/ai-native-engineering-workspace/change"><img src="https://agentmods.dev/badge/commands/engindemirog/ai-native-engineering-workspace/change.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.00024 | $0.00425 |
| Opus 5.5 | $0.00010 | $0.00170 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
change 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 22d 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.
What it actually says
Read AGENTS.md, workflows/change-request.md, and workflows/segments.md. Handle this change request: $ARGUMENTS
- TRIAGE. Apply the three-question rubric in change-request.md, in its order, as written. Present the verdict (BUG / TRIVIAL / CHANGE) WITH your rationale (proposal rule) and wait for my confirmation. Read the trivial-change policy from docs/git.md ("Trivial changes") first.
- BUG → say so, point me to /fix-bug with the report, and STOP.
- TRIVIAL → restate the policy from docs/git.md, then run the trivial lane: one narrow commit, ./scripts/check green, PR/reviewer as the policy says. If it needs a second file or a new test, stop and re-triage.
- CHANGE → twin check first: if a spec in specs/active/ carries the same "Source:" key,
show it and ask whether to resume it — never open a second one. Then read the Mode:
- strict → run only the ANALYZE segment with specs/TEMPLATE-mini.md (Source mandatory, changed + preserved criteria, Supersedes if a shipped spec exists), wait for spec approval, set "Status: Approved", write the handoff "Next: PLAN — Developer runs /plan ", STOP.
- lite → chain ANALYZE (mini) → /plan → /build → /review (narrow) → /verify (before/after screenshots for UI) → ship, asking at every gate. Entry checks stay: /plan needs the Approved spec, /build needs the filled "Approved by / on" line — the plan gate is never skipped in this lane.
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.
- 22d ago First seen · 24 lines · 24 tokens per session scan A 4060fc320006
change is a command published in the GitHub repository engindemirog/ai-native-engineering-workspace (87 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 425 once invoked, about $0.0001 per session on Opus 5.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-26.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.