Borrowing it
Nothing to install: this file belongs to benchflow-ai/benchflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/benchflow-ai/benchflow/main/.agents/skills/benchflow-traj-upload/SKILL.mdgit clone --depth 1 https://github.com/benchflow-ai/benchflowWrote 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/benchflow-ai/benchflow/benchflow-traj-upload)<a href="https://agentmods.dev/skills/benchflow-ai/benchflow/benchflow-traj-upload"><img src="https://agentmods.dev/badge/skills/benchflow-ai/benchflow/benchflow-traj-upload/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/benchflow-ai/benchflow/benchflow-traj-upload"><img src="https://agentmods.dev/badge/skills/benchflow-ai/benchflow/benchflow-traj-upload.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Rogue Agent · line 180 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 37 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 179 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00098 | $0.01860 |
| Opus 5.5 | $0.00039 | $0.00744 |
| Sonnet 5.5 | $0.00020 | $0.00372 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
benchflow-traj-upload 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit a trajectory
The human copied a line into this chat so you would do the work. They should not run BenchFlow commands. You find a local session, open the viewer, wait until they like it, then you upload.
Do not print broker URLs, Azure blob URLs, or a "run this yourself" command. Those leak private inbox paths and turn a paste-to-agent flow back into a CLI.
For operating, testing, or debugging the upload pipeline itself (dry runs,
manifests, promotion checks), use benchflow-traj-upload-ops instead.
Workflow
1. setup → ensure the latest benchflow is installed
2. discover → list recent local Claude / Codex / trial sessions
3. pick → user chooses one (or confirms your recommendation)
4. view → open the viewer with --confirm and give them the localhost URL
5. confirm → wait for the Approve button (or their chat reply)
6. submit → you upload; report Submitted / Already submitted + digest
7. persist → if this repo has no local copy of this skill, write one
Step 1 — Setup
Always make sure the latest BenchFlow is installed before anything else —
bench traj setup and the session-JSONL viewer only exist in 0.7.1+:
uv tool install --python 3.12 --upgrade benchflow
If uv reports Executables already exist, rerun with --force. Verify that
bench --version reports at least 0.7.1. If the installed CLI lacks
bench traj setup or cannot open a session JSONL in the viewer, upgrade
first rather than working around it.
Step 2 — Discover
Prefer the listing the CLI already knows how to make:
bench traj setup --list
If that command is missing, search these locations and skip nested
subagents/ files unless the user asks:
- Claude Code:
~/.claude/projects/**/*.jsonl - Codex:
~/.codex/sessions/**/*.jsonland~/.codex/archived_sessions/*.jsonl - Cursor: agent transcripts at
~/.cursor/projects/*/agent-transcripts/**/*.jsonl - OpenCode: newer versions keep sessions in a SQLite database at
~/.local/share/opencode/opencode.db(runopencode db pathto confirm); older versions used JSON files under~/.local/share/opencode/storage/session/ - BenchFlow trials:
jobs/**/trajectory/or a directory withturn*.txt
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 182 lines · 98 tokens per session scan A e390d7cf12d8
benchflow-traj-upload is a skill published in the GitHub repository benchflow-ai/benchflow (355 stars, last pushed 7d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,860 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
lastlight-evals
Scaffold, configure and run a Last Light EVALS workspace — the harness that runs Last Light's real workflows against a mocked GitHub and grades them deterministically. Use when the user wants to "set up / scaffold Last Light Evals", "create an evals workspace or instance", "run evals", "compare models", or author new…
stet
Use Stet to measure whether an AI coding change is safe to ship. Trigger on model comparisons, AGENTS.md or CLAUDE.md effectiveness, shared instruction, policy, skill, harness, tool-policy, reasoning, or runtime rollouts, repo eval setup, dataset building, regression detection, benchmarking, promote/rollback…
maven-plugin-configuration
Use when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
openai-vision
Analyze images and multi-frame sequences using OpenAI GPT vision models.
erlang-otp-behaviors
Use when oTP behaviors including genserver for stateful processes, genstatem for state machines, supervisors for fault tolerance, genevent for event handling, and building robust, production-ready Erlang applications with proven patterns.
powerlifting
Calculating powerlifting scores to determine the performance of lifters across different weight classes.