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 natsukium/dotfiles --skill fjgit clone --depth 1 https://github.com/natsukium/dotfilesWrote 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/natsukium/dotfiles/fj)<a href="https://agentmods.dev/skills/natsukium/dotfiles/fj"><img src="https://agentmods.dev/badge/skills/natsukium/dotfiles/fj.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Privilege Escalation · line 39 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00058 | $0.01557 |
| Opus 5 | $0.00029 | $0.00779 |
| Sonnet 5 | $0.00012 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
fj 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 today.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fj - Forgejo CLI
Use fj for Forgejo-specific operations on git.natsukium.com. Use git for local commits, branches, and pushes.
Select the host and repository explicitly
For unattended commands, avoid checkout inference and provide both the public host and repository:
fj -H https://git.natsukium.com issue search --repo owner/repo
fj -H https://git.natsukium.com issue view 'owner/repo#42'
Repository syntax depends on the command:
- Collection and create commands for issues and PRs accept
--repo owner/repo. - Commands acting on an existing issue accept a positional qualified reference such as
'owner/repo#42'. - Most commands acting on an existing PR accept the same qualified form.
pr assignandpr unassigntake it through--prinstead. - Repository commands generally take
owner/repoas a positional argument. Releases, tags, Actions, and wikis expose their own global--repo; check the relevant--helpbefore composing less common commands. - Convert a URL such as
https://git.natsukium.com/owner/repo/issues/42or/pulls/42to'owner/repo#42'.
-C, -R, and the current directory infer the instance and repository from a Git remote. Prefer -H with --repo (or a qualified reference) over -R for unattended commands: -R resolves the named remote and takes precedence over -H, and an SSH remote host is resolved through OpenSSH config, so a HostName rewrite to the internal host makes fj dial https:// on a host that does not serve it. If a command fails against the internal host, retry with -H https://git.natsukium.com and an explicit repository or qualified reference instead of connecting Tailscale; reserve -R for deliberate checkout inference.
Authentication
fj auth list
fj -H https://git.natsukium.com whoami
fj auth login -H https://git.natsukium.com
fj auth add-token -H https://git.natsukium.com # reads the token from stdin when omitted
fj auth logout -H https://git.natsukium.com
fj auth list should include git.natsukium.com. Never print or place an access token directly in a recorded command.
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.
- today Changed · +3 lines 831e5ae32057
- yesterday First seen · 100 lines · 58 tokens per session scan A 6fd367033bc3
fj is a skill published in the GitHub repository natsukium/dotfiles (103 stars, last pushed today), licensed CC0-1.0. It adds 58 tokens to every session and 1,557 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-06.
Other skills, from other repositories
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".
github-workflow
Professional GitHub issue/PR workflow with gh CLI. Use when a best-practice use case needs issue → PR → Closes.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
sync-release
Owns release-pipeline conventions: sr.yaml schema, the sr CLI verbs (init/plan/prepare/ release) and urmzd/sr action, typed publishers (cargo/npm/pypi/docker/go/custom), monorepo workspace discovery, versionfiles/stagefiles mapping, and post-release patterns. Language-specific build targets live in scaffold-rust…
setup-ci
Defines GitHub Actions workflow structure: ci.yml + release.yml naming, concurrency groups, bot-commit skip, workflowcall reuse, App-token checkout, and optional fsrc/teasr steps. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up…
release-audit
Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking…