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 skills add IvanLutsenko/awac-ai-agent-plugins --skill project-archivegit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/project-archive)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/project-archive"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/project-archive/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/ivanlutsenko/awac-ai-agent-plugins/project-archive"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/project-archive.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.00028 | $0.00413 |
| Opus 5.5 | $0.00011 | $0.00165 |
| Sonnet 5.5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
obsidian-tracker-project-archive 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 14d 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
Converted from Claude Code command
/project-archive. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Manage project lifecycle: archive, restore, or permanently delete projects.
Input: $ARGUMENTS
Parse action and project name from arguments. If action is not provided, ask the user which action they want: archive, restore, or delete.
Actions
archive
- Call
listProjects(without includeArchived) to show active projects - If project name not provided, ask user to choose
- Confirm with user before archiving
- Call
archiveProjectwith the project name - Report result
restore
- Call
listProjectswithincludeArchived: true - Show only archived projects (where
archived: true) - If no archived projects, inform user and stop
- If project name not provided, ask user to choose
- Call
restoreProjectwith the project name - Report result
delete
- Call
listProjectswithincludeArchived: true - Show archived projects first (preferred deletion targets)
- If project name not provided, ask user to choose
- Always confirm with explicit warning: this action is irreversible, all data will be lost
- Call
deleteProjectwith the project name and appropriatefromArchiveflag - Report result
Codex differences
- A non-interactive run (
codex exec, CI) has nobody to answer a prompt: continue on defaults, honour whatever the invoking prompt already specified, and report which defaults were used. If the whole point of the command is to ask, say that it needs an interactive session and stop rather than inventing answers.
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.
- 14d ago Changed · +4 lines 93e00e99032f
- 1mo ago First seen · 40 lines · 28 tokens per session scan A a17bc0f663c9
obsidian-tracker-project-archive is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 413 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-05.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…