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 growthxai/output --skill output-meta-post-flightgit clone --depth 1 https://github.com/growthxai/outputWrote 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/growthxai/output/output-meta-post-flight)<a href="https://agentmods.dev/skills/growthxai/output/output-meta-post-flight"><img src="https://agentmods.dev/badge/skills/growthxai/output/output-meta-post-flight/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/growthxai/output/output-meta-post-flight"><img src="https://agentmods.dev/badge/skills/growthxai/output/output-meta-post-flight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01011 |
| Opus 5 | $0.00016 | $0.00505 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
output-meta-post-flight 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Flight Rules for Output SDK Workflows
Execution Verification
After completing all steps in the process_flow, systematically verify:
Step Completion Audit
- Every numbered step has been read, executed, and delivered according to its instructions
- All steps that specified a subagent were delegated to the correct subagent
- If any subagent was not used as specified, document why and report to the user
- If any step was not executed according to instructions, explain which part was misread or skipped
Output SDK Convention Compliance
Verify the following conventions were followed:
Import Conventions
- All TypeScript/JavaScript imports use
.jsextension for ES modules - No direct axios usage - HttpClient wrapper used throughout
- Proper import paths for Output SDK packages (@outputai/core, @outputai/llm, etc.)
Workflow Structure
- Workflow exported in entrypoint.ts:
export * from './path/to/workflow.js'; - All external operations wrapped in Temporal activities (steps)
- Proper error handling with ApplicationFailure patterns
- Retry policies configured appropriately
Schema Placement
- All schemas for
aiSdk.Output.object()defined intypes.ts, not inline in step functions - LLM output schemas use
.describe()only -- no.min()/.max()/.length()on numbers or arrays - Prompt files do not contain JSON output format instructions when
aiSdk.Output.object()is used
LLM Provider & Variables
- All prompt files use the same provider (no mixing unless explicitly requested)
- Structured
generateText/Agentvariables use Liquid loops, conditions, or dot notation appropriately
Code Style (see output-dev-code-style)
- No trailing commas in any generated code
- No
letdeclarations -- all variables useconst - Arrow functions use parens only when needed (multi-param or destructured)
- Operator linebreaks placed after the operator, not before
- Space in parens:
fn( x )notfn(x)
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.
- 11d ago First seen · 111 lines · 32 tokens per session scan A 057ad2b62813
output-meta-post-flight is a skill published in the GitHub repository growthxai/output (435 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 1,011 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ax-agent-rlm
This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions…
ax-agent
This skill helps an LLM generate correct core AxAgent code using @ax-llm/ax. Use when the user asks about agent(), child agents, namespaced functions, discovery mode, clarification, bubbleErrors, host-side final/clarification protocol, or ordinary agent runtime behavior. For MCP clients, native runtime modules…
ax-ai
This skill helps an LLM generate correct AI provider setup and configuration code using @ax-llm/ax. Use when the user asks about ai(), providers, models, routing, adaptive balancing, presets, embeddings, batch audio with ai.transcribe() or ai.speak(), extended thinking, context caching, or mentions…
ax-flow
This skill helps an LLM generate correct AxFlow workflow code using @ax-llm/ax. Use when the user asks about flow(), AxFlow, workflow orchestration, parallel execution, DAG workflows, conditional routing, map/reduce patterns, or multi-node AI pipelines.
ax-agent-memory-skills
This skill helps an LLM generate correct AxAgent memory retrieval, context-map, and dynamic skill-loading code using @ax-llm/ax. Use when the user asks about contextMap, AxAgentContextMap, onMemoriesSearch, memoriesCatalog, recall(...), inputs.memories, onLoadedMemories, onUsedMemories, onSkillsSearch, skillsCatalog…
ax-agent-optimize
This skill helps an LLM generate correct AxAgent tuning and evaluation code using @ax-llm/ax. Use when the user asks about agent.optimize(...), judgeOptions, eval datasets, optimization targets, saved optimizedProgram artifacts, or agent optimization guidance.