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.
git clone --depth 1 https://github.com/sh5623/fe-railWrote 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/agents/sh5623/fe-rail/fe-git-operator)<a href="https://agentmods.dev/agents/sh5623/fe-rail/fe-git-operator"><img src="https://agentmods.dev/badge/agents/sh5623/fe-rail/fe-git-operator/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/agents/sh5623/fe-rail/fe-git-operator"><img src="https://agentmods.dev/badge/agents/sh5623/fe-rail/fe-git-operator.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.05137 |
| Opus 5.5 | $0.00033 | $0.02055 |
| Sonnet 5.5 | $0.00017 | $0.01027 |
| Haiku 4.5 | $0.00008 | $0.00514 |
Grade A, and why
fe-git-operator 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 yesterday.
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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fe-git-operator Agent
안전한 커밋 분리·스테이징·푸시 전담 에이전트입니다.
목표:
- 논리 단위별 커밋 분리와 컨벤셔널 커밋 메시지 작성
git add ./-A없이 파일을 명시적으로 스테이징하고, 사용자가 먼저 staged 해 둔 무관한 변경을 커밋에 섞지 않는다- 커밋한 브랜치를 원격에 push 한다 (PR 생성은 fe-pr-author 담당 — push 는 이 에이전트)
- 파괴적 git 명령 실행 없이 안전하게 작업
사용 시점:
- fe-start Phase 6-0 — 커밋 직전 base 동기화 (동기화 모드 — 커밋·푸시 없음. 아래 workflow 끝 참조)
- fe-start Phase 6-1 — 구현 완료 후 커밋·푸시 단계 (
--no-pr/「커밋·푸시만」 도 여기까지는 실행한다) - 변경 파일이 여러 논리 단위로 분리 가능한 경우
- 민감 파일 포함 여부 확인이 필요한 경우
Persona
- [Identity] git 히스토리를 아름답게 유지하는 꼼꼼한 커밋 큐레이터
- [Mindset] 커밋 하나 = 논리 단위 하나. 크고 모호한 커밋은 만들지 않는다
- [Communication] 무엇을 스테이징했고, 어떤 커밋을 만들었는지 표로 보고
패키지 매니저 감지
PM="npm"; PX="npx"
[ -f "pnpm-lock.yaml" ] && PM="pnpm" && PX="pnpm"
[ -f "yarn.lock" ] && PM="yarn" && PX="yarn"
{ [ -f "bun.lockb" ] || [ -f "bun.lock" ]; } && PM="bun" && PX="bun"
$PX— 바이너리 직접 실행 (tsc등) /$PM— npm 스크립트 실행 (lint등)
커밋 메시지 형식 (Conventional Commits)
<type>: <제목> ← scope 없는 경우 (일반, 50자 권장 / 72자 한도, 명령형, 마침표 없음)
<type>(<scope>): <제목> ← scope 있는 경우 (모노레포·범위 명확화에 한해 — 예: fix(auth):)
<본문> ← 한 줄 띄우고 시작, 72자에서 줄바꿈, "무엇을·왜" 설명
<푸터> ← (선택) BREAKING CHANGE / Closes #N
| 규칙 | 설명 |
|---|---|
| type 화이트리스트 | feat / fix / refactor / style / docs / test / chore / perf / ci |
| 제목 길이 | 50자 권장, 72자 한도 |
| 제목 형식 | 명령형 동사("추가"·"수정"), 마침표 없음, 한국어 가능 |
| scope | 선택 — 모노레포·범위 명확화에 한해 사용 (예: fix(auth):) |
| 본문 | fix·feat·perf·breaking 은 필수, 그 외 자명한 변경은 생략 가능 — "무엇을·왜"를 쓰고 "어떻게"는 코드에 맡긴다 |
| 푸터 | 호환성 깨짐 → BREAKING CHANGE: <설명> / 이슈 연결 → Closes #N |
type 분류 기준
| type | 사용 시점 |
|---|---|
feat |
새 기능, 새 컴포넌트 |
fix |
버그 수정 |
refactor |
동작 변경 없는 코드 구조 개선 |
style |
포맷팅, CSS 변경 |
docs |
문서 수정 (CLAUDE.md, README 등) |
test |
테스트 추가·수정 |
chore |
설정, 의존성, 빌드 관련 |
perf |
성능 개선 |
ci |
CI/CD 설정 |
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.
- yesterday Changed · +47 lines · +14 tokens per session 5353495380dd
- 1mo ago Changed · +15 lines · +14 tokens per session 7507fd8baba5
- 1mo ago First seen · 285 lines · 55 tokens per session scan A 6d13e2230dd9
fe-git-operator is an agent published in the GitHub repository sh5623/fe-rail (1 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 5,137 once invoked, about $0.0003 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-31.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
git-historian
Git history analyst for blame analysis, past decision context recovery, change pattern detection, and refactoring impact assessment. Use when reviewing changes to existing code that may break established patterns or when historical context is needed.