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-workflow-trace-filegit 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-workflow-trace-file)<a href="https://agentmods.dev/skills/growthxai/output/output-workflow-trace-file"><img src="https://agentmods.dev/badge/skills/growthxai/output/output-workflow-trace-file/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-workflow-trace-file"><img src="https://agentmods.dev/badge/skills/growthxai/output/output-workflow-trace-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 48 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00055 | $0.00635 |
| Opus 5 | $0.00028 | $0.00318 |
| Sonnet 5 | $0.00011 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
output-workflow-trace-file 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show just the final output of an Output.ai workflow trace — the actual result, rendered as readable markdown.
The argument the user provided is either a workflow name (e.g. context_competitors) or a workflow run ID. If no argument is provided, use the most recent trace across all workflows.
Instructions
-
Find the trace JSON file:
- Trace files live in
logs/runs/<workflow_name>/as JSON files - Filenames follow the pattern:
<timestamp>_<workflow_id>.json - If a workflow name is given, find the latest
.jsonfile inlogs/runs/<workflow_name>/ - If a run ID is given, search across all
logs/runs/*/folders for a file containing that ID in its filename - If no argument, find the most recently modified
.jsonfile across alllogs/runs/*/folders
- Trace files live in
-
Extract the output from the trace file. You only need
outputfrom the JSON root — skipchildrenandinput.Strategy for large files (trace files can be 10k+ lines):
- First, try
jq '.output' <file>to extract directly — this is the fastest path - If
jqis not available: read the last 500 lines of the file (theoutputfield is at the root level, near the end of the JSON). Work backwards in chunks if needed - Do NOT read the entire file from the top — the
childrenarray with step details can be thousands of lines and you don't need any of it
- First, try
-
Save a markdown file to
tmp/trace_result_<workflow_name>_<id>.md(create thetmp/directory if it doesn't exist) with:Header (brief)
- One line: workflow name, ID, duration
Result
Render
outputas clean, readable markdown:- String fields that contain markdown → render directly
- Arrays of objects → render each as a sub-section with key fields
- Arrays of strings → numbered lists
- Nested objects → sub-sections with key-value pairs
- URLs → render as links
- Long text excerpts → render as blockquotes
The goal is a document you'd want to READ, not debug. Make it look good.
-
Tell the user the saved file path.
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.
- 5d ago First seen · 49 lines · 55 tokens per session scan A 1e06637824bb
output-workflow-trace-file is a skill published in the GitHub repository growthxai/output (435 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 635 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
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-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-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.