Borrowing it
Nothing to install: this file belongs to BariBariGood/manzanas. 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/BariBariGood/manzanas/main/.agents/skills/journal-evidence-export/SKILL.mdgit clone --depth 1 https://github.com/BariBariGood/manzanasWrote 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/baribarigood/manzanas/journal-evidence-export)<a href="https://agentmods.dev/skills/baribarigood/manzanas/journal-evidence-export"><img src="https://agentmods.dev/badge/skills/baribarigood/manzanas/journal-evidence-export/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/baribarigood/manzanas/journal-evidence-export"><img src="https://agentmods.dev/badge/skills/baribarigood/manzanas/journal-evidence-export.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 Data Exfiltration · line 62 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00063 | $0.00887 |
| Opus 5.5 | $0.00025 | $0.00355 |
| Sonnet 5.5 | $0.00013 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
journal-evidence-export scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s $D/v0/journal/$LID/export.md > evidence.md # same markdown, raw HTTP How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal evidence export
Every mutating op under a lease is journaled (append-only JSONL + content-
addressed artifacts). The run ID is the lease ID, so you always know your
run without extra bookkeeping. Journal-disabled daemons (--journal-dir "")
answer 501 on all of these.
The one-call PR evidence export
manzanas journal export $LID -o evidence.md # or: --format json
curl -s $D/v0/journal/$LID/export.md > evidence.md # same markdown, raw HTTP
Returns a PR-comment-ready markdown summary: run metadata (agent, purpose,
target, runtime), an ordered action table with failures highlighted, and
the artifact list. Paste it into the PR body or a comment. Works after the
lease is released. --journal-dir ~/.manzanasd/journal exports offline
straight from the on-disk store (daemon stopped, or a copied run dir).
MCP agents have the same export as the journal_export tool; the GitHub
Action posts it automatically with journal-evidence: "true".
Inspect a run
curl -s $D/v0/journal | jq '.runs[0]' # newest runs first
curl -s "$D/v0/journal/$LID?limit=100" | jq '.entries[] | .payload.action'
# next_seq != 0 → pass it back as from_seq for the next page
Entry kinds: lease, action, observation, state, segment. HID
actions record ax_before/ax_after tree hashes when dispatched with
payload "ax_hashes": true — cheap before/after UI evidence.
Fetch artifacts (screenshots)
A successful screenshot action is stored automatically; entries carry
artifacts: [{path, sha256, bytes}]:
curl -s "$D/v0/journal/$LID?limit=1000" \
| jq -r '.entries[].payload.artifacts[]?.path'
curl -s -o shot.png "$D/v0/journal/$LID/artifacts/artifacts/<sha256>.png"
Tip: dispatch screenshots with "inline": false to keep responses small and
pull the bytes from the journal afterwards.
Upload your own evidence
While the lease is still active (immutable after release/expiry — upload before you release):
manzanas journal upload $LID shot1.png shot2.png # --kind observation|screenshot|video
# or raw HTTP:
curl -s -X POST "$D/v0/journal/$LID/artifacts?name=final-state&kind=screenshot" \
--data-binary @shot.png
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 · 87 lines · 63 tokens per session scan A c84955e99d15
journal-evidence-export is a skill published in the GitHub repository BariBariGood/manzanas (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 887 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ios-simulator-interaction
Interaction with the iOS simulator using iosef, a CLI optimized for agent usage. Use when building or testing changes on the iOS Simulator — viewing the screen, tapping buttons, reading accessibility trees, finding elements by selector, asserting UI state, scripting multi-step test flows, installing and launching…
testa
Autonomously E2E-test iOS apps in the Simulator — read the screen (accessibility tree OR on-device OCR), tap/type/swipe/drag-drop/pinch/rotate, manage apps, and assert results. Use when asked to test, QA, drive, or reproduce a flow in an iOS app/simulator (React Native, Expo, native SwiftUI, or any app).…
verify-vibebuddy
Drive VibeBuddy (Mac menu-bar companion, headless vibebuddyd on the LAN HTTP surface, iPhone, Watch) the way a user does. Use to launch an isolated daemon, prove dashboard sessions, phone pairing, remote approval, question reply, or iPhone Demo, and capture evidence without touching the installed app on :9876.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
ios-simulator-skill
Build, test, and drive iOS apps in the Simulator with 30 token-efficient scripts. Use when asked to build or test an Xcode project, launch an app on a simulator, tap/type/swipe through its UI by accessibility label, take screenshots or visual diffs, audit accessibility, read logs or diagnose hangs, or manage…
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.