deployable-inventory

A deployment inventory that lists the evidence required for each deployable system before claiming a release or deployment happened.

In plain words
What is it for?
Use it when changing runtime settings or release workflows and when verifying deployment claims.
Why use it?
A successful build only proves that an artifact was created, not that it was released or deployed.

Agent

Install

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.

agentmods
npx agentmods add agents/getopenpost/openpost/deployable-inventory
Clone the repo
git clone --depth 1 https://github.com/getopenpost/openpost
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,007 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01007
Opus 5 $0.00000 $0.00504
Sonnet 5 $0.00000 $0.00201
Haiku 4.5 $0.00000 $0.00101

Measured yesterday against content hash 0dd7569ca878, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deployable-inventory 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 yesterday.

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.

docs/agents/deployable-inventory.md · 15 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 15 lines · 0 tokens per session scan A 0dd7569ca878

Subscribe to this mod's changes

deployable-inventory is an agent published in the GitHub repository getopenpost/openpost (38 stars, last pushed today), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 1,007 tokens. 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.

Related

Other agents, from other repositories

AGENT_RUNTIME

Commonly is a platform-only core. Agents run externally and connect to Commonly using runtime tokens.

Team-Commonly/commonly · 0 tokens

LOCAL_CLI_WRAPPER

Wrap any locally-installed AI agent CLI (claude, codex, cursor, gemini, …) as a Commonly pod participant. Your laptop becomes the runtime; Commonly provides identity, memory, and the social surface.

Team-Commonly/commonly · 0 tokens

AGENT_AUTONOMY

Purpose: Dev agents (Theo/Nova/Pixel/Ops) autonomously source tasks from GitHub, implement them with acpxrun, and open PRs — without human direction.

Team-Commonly/commonly · 0 tokens

NATIVE_RUNTIME

The native runtime executes agents in-process inside the Commonly backend, using LiteLLM as the LLM gateway. No external process, no container, no gateway — the agent runs as a function call inside the Node.js server.

Team-Commonly/commonly · 0 tokens

clawdbot-pin-and-the-cycles-outage

Status: RESOLVED 2026-08-05 by #840, and guarded in CI by scripts/verify-moltbot-tool-contract.js. Kept because the failure mode is durable, the guard is young, and this file is the only record of how three separate people were confidently wrong about the same 25-tool block in both directions.

Team-Commonly/commonly · 0 tokens

AGENT_CODING_CAPABILITY

This doc exists because the answer to "why can't my OpenClaw agent just write the code?" is non-obvious and has bitten us in production. It is the source of truth for the runtime → coding-capability mapping.

Team-Commonly/commonly · 0 tokens