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 Unique-Divine/jiyuu --skill justfilegit clone --depth 1 https://github.com/Unique-Divine/jiyuuWrote 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/unique-divine/jiyuu/justfile)<a href="https://agentmods.dev/skills/unique-divine/jiyuu/justfile"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/justfile.svg" alt="Measured on agentmods" height="20"></a>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.00068 | $0.01366 |
| Opus 5 | $0.00034 | $0.00683 |
| Sonnet 5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
just 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 7d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Just
Use this skill when a repo may expose commands through justfile.
Treat just as the canonical task interface when it exists. Prefer existing
recipes over reconstructing the underlying go, npm, cargo, docker,
make, or shell commands by hand.
When To Use This Skill
Use it when:
- the repo or a nearby subproject has a
justfile - the user asks how to build, test, lint, run, deploy, or inspect commands
- the user mentions
just,justfile, recipes, or recipe arguments - the repo has both
Makefileandjustfileand you need to understand which command surface is intended - the user wants to migrate from
maketojust
Default Workflow
- Find the nearest relevant
justfile. Do not assume repo root. - Run
just --listin that directory to discover the supported UX. - If a recipe is unclear, inspect it with
just --show <recipe>. - Use the recipe directly unless the user explicitly wants the raw command.
- Fall back to ad hoc commands only when no suitable recipe exists.
Common recipe names to check first: setup, install, build, test, lint,
fmt, dev, run, preview, deploy.
Agent Guardrails
- Prefer the nearest task-specific
justfileover a broader root-level one. - If both
Makefileandjustfileexist, inspect both before suggesting migration or replacement. - Do not bypass an existing recipe unless it is missing, clearly wrong for the task, or the user asks for the underlying command.
- Do not assume
.envexists, and do not print secrets just because ajustfileusesdotenv-loador exported variables. - Treat destructive or confirmation-gated recipes cautiously.
- Test-like shebang recipes (
test,test-*, etc.) should use#!/usr/bin/env bashandset -euo pipefailso failures propagate instead of being masked by later commands. - Recipe doc comments must be exactly one
# ...line immediately above the recipe name.just/just --listuse only that adjacent comment as the recipe description; a second#line replaces or truncates the intended preview text.
What ships with it
2 files 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.
- 7d ago First seen · 149 lines · 68 tokens per session scan A 1e480806f014
just is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 25d ago), licensed MIT. It adds 68 tokens to every session and 1,366 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-08-31.
Other skills, from other repositories
extension-upload
Package a script tool under /.config/agenvoy/tools/script/ into a tar.gz and publish to pkg.agenvoy.com registry. Keyword picker, dep/key detection, config-stored email (ask + lowercase + persist), ask version, email verification gate, multipart upload with downgrade/unique guards.
e2a
Use when operating an already-connected e2a inbox over MCP: reading, composing, sending, replying, forwarding, handling attachments, managing contacts/outreach, scheduling mail, or using templates. Teaches correct threading, conversation correlation, concise multipart composition, and accepted/pending-review no-retry…
notion-cli
Work with Notion from the terminal using the notion CLI. Use when the user needs to read, create, update, query, or manage Notion pages, databases, blocks, comments, users, or files programmatically. Covers the entire Notion API with 50+ commands. Triggers: Notion workspace automation, database queries, page creation…
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
context-setup
Build, import, or refresh this workspace's identity, project, reusable-workflow, and weekly-state files through a guided review. Use only when the user explicitly asks to initialize or redo workspace context.