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 event4u-app/agent-config --skill file-editorgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/file-editor)<a href="https://agentmods.dev/skills/event4u-app/agent-config/file-editor"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/file-editor/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/event4u-app/agent-config/file-editor"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/file-editor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Excessive Agency · line 164 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 165 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00030 | $0.01790 |
| Opus 5 | $0.00015 | $0.00895 |
| Sonnet 5 | $0.00006 | $0.00358 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
file-editor 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
file-editor
When to use
This skill applies automatically whenever:
- The agent creates or edits a file using
save-fileorstr-replace-editor - The agent wants to show the user a file they should review
Do NOT use when:
- Only reading files (no edits)
- Running commands or tests
- The
personal.open_edited_filessetting isfalse
Procedure: Open files in IDE
- Read settings — Check
personal.open_edited_filesandpersonal.idein.agent-settings.yml. - Skip if disabled — If
personal.open_edited_filesisfalse, do nothing. - Open files — Use the IDE CLI command to open each edited file.
- Verify — Confirm the command succeeded (exit code 0).
Settings file
Settings are stored in .agent-settings.yml (project root, git-ignored).
See .augment/templates/agent-settings.md for the full settings reference.
Relevant settings for this skill:
| Key | Values | Default | Description |
|---|---|---|---|
personal.ide |
code, cursor, windsurf, phpstorm, webstorm, idea, goland, rubymine, pycharm, rider, subl, vim, nvim, emacs, zed |
(empty) | CLI command to open files |
personal.open_edited_files |
true, false |
false |
Whether to auto-open edited files |
Behavior
1. Read settings
At the start of a conversation (or on first file edit), read .agent-settings.yml:
cat .agent-settings.yml 2>/dev/null
- If the file doesn't exist → do not open files. Suggest running
scripts/install(then/onboard). - If
personal.open_edited_files: false→ do nothing. - If
personal.open_edited_files: trueandpersonal.ideis set → open files after edits.
2. Open files after edits
After editing one or more files, open them using the ide setting.
Always jump to the first edited line. The syntax depends on the IDE:
JetBrains IDEs (personal.ide: phpstorm / webstorm / idea / pycharm / goland / rubymine / rider):
phpstorm --line {line} {file} # PHP
webstorm --line {line} {file} # JS / TS
idea --line {line} {file} # Java / Kotlin / general
pycharm --line {line} {file} # Python
goland --line {line} {file} # Go
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 · 175 lines · 30 tokens per session scan A dce8ce00e466
file-editor is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,790 once invoked, about $0.0002 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
next-action
Use when the user wants a next-action recommendation based on current state — reads handoff/git/lessons/STATE and proposes top-3 by impact. Trigger: '/next', 'what should I do next', 'next action'. Proposes only, never executes.
lov-canonical-store
A central file and command-line workflow for maintaining one deduplicated vocabulary list as the source for other apps.
feishu-interaction
Feishu/Lark platform interaction via MCP - documents, tasks, calendar, Bitable, messaging.