Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitnpx agentmods add skills/davidmatousek/agentic-oriented-development-kit/aod-statusWrote 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/davidmatousek/agentic-oriented-development-kit/aod-status)<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-status"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-status/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/skills/davidmatousek/agentic-oriented-development-kit/aod-status"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-status.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.00057 | $0.00856 |
| Opus 5.5 | $0.00023 | $0.00342 |
| Sonnet 5.5 | $0.00011 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
~aod-status 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 1mo 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.
This is a copy
100% identical to ~aod-status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AOD Status Skill
Purpose
Utility skill for the AOD Lifecycle. Provides an on-demand snapshot of the project backlog by regenerating BACKLOG.md from GitHub Issues and displaying a summary of items per lifecycle stage.
No governance gates — this is a read-only utility command.
How It Works
Step 1: Reconcile Board
Run board reconciliation to fix any label↔board column drift before generating the snapshot:
source .aod/scripts/bash/github-lifecycle.sh && aod_gh_reconcile_board
This compares each open issue's stage:* label to its board column and fixes mismatches. If the board or gh is unavailable, it skips silently.
Step 2: Regenerate BACKLOG.md
Run the backlog regeneration script with JSON output mode:
bash .aod/scripts/bash/backlog-regenerate.sh --json
Parse the JSON output to extract:
file: path to regenerated BACKLOG.mdtotal: total number of GitHub Issuesstages: object with counts per stage (discover,define,plan,build,deliver,untracked)
If the script fails or gh is unavailable: Display a warning and attempt to read the existing BACKLOG.md file instead. If no BACKLOG.md exists either, report that no backlog data is available.
Step 3: Display Stage Summary
Present a formatted summary table:
AOD LIFECYCLE STATUS
| Stage | Count |
|----------|-------|
| Discover | {n} |
| Define | {n} |
| Plan | {n} |
| Build | {n} |
| Deliver | {n} |
| Untracked| {n} |
|----------|-------|
| Total | {n} |
BACKLOG.md regenerated at {file_path}.
Step 4: Show Active Feature Context (Optional)
If the current git branch matches a feature pattern (NNN-*), display the active feature context:
- Get branch:
git branch --show-current - Extract NNN prefix
- Check for
specs/{NNN}-*/directory - If found, read spec.md/plan.md/tasks.md frontmatter to show approval status:
Active Feature: {NNN}-{name}
spec.md: {PM approved / not approved / missing}
plan.md: {dual approved / not approved / missing}
tasks.md: {triple approved / not approved / missing}
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.
- 1mo ago First seen · 102 lines · 57 tokens per session scan A 225968d9252b
~aod-status is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 856 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ~aod-status, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…