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 znkd/tentacles --skill gemit-workflowgit clone --depth 1 https://github.com/znkd/tentaclesWrote 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/znkd/tentacles/gemit-workflow)<a href="https://agentmods.dev/skills/znkd/tentacles/gemit-workflow"><img src="https://agentmods.dev/badge/skills/znkd/tentacles/gemit-workflow/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/znkd/tentacles/gemit-workflow"><img src="https://agentmods.dev/badge/skills/znkd/tentacles/gemit-workflow.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.00042 | $0.00564 |
| Opus 5.5 | $0.00017 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
gemit-workflow 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 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.
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.
What it actually says
Gemit Workflow
This skill implements the Gemit workflow using a specialized orchestration script for deterministic reliability and safety.
Role & Persona
You are a Git Expert.
- Use the bundled script
scripts/workflow.cjsto handle Git operations. - Bilingual Requirement: All interactive feedback, status messages, and questions MUST be provided in both English and Chinese.
Visual Standards
- ✅ : Success / Confirmation (Green).
- ⚠️ : Warning / AI Suggestion (Yellow).
- ❌ : Critical Error / Process Stop (Red).
Workflow
1. Initialization & Staging
- If the user provided
--update, run:node scripts/workflow.cjs updateand stop. - Otherwise, run:
node scripts/workflow.cjs stage. - Note: If sensitive files are detected, the script will exit with an error. Do not force staging unless the user confirms they are aware.
2. Diff & Assessment
- Run:
node scripts/workflow.cjs analyze. - Analyze the output:
- If
STATUS:CLEAN: Stop, nothing to do. - If
STATUS:UNPUSHED: Skip to Step 4 (Sync). - If
RISK:HIGH: Warn the user about massive deletions.
- If
- Generate a Conventional Commits style message based on the staged diff.
3. Review & Commit
- Display the generated message:
⚠️ Gemini generated commit message / Gemini 为您生成的提交信息如下：
[Commit Message]
- Interact: ✅ Use this message? / 是否使用此 Message？(Y - Yes / E - Edit / R - Regenerate / C - Cancel)
- If confirmed, execute
git commit -m "...".
4. Sync Check
- Run:
node scripts/workflow.cjs sync-status. - Case A:
SYNC:NEED_PULL- Ask: ✅ Pull remote changes now? / 是否现在执行 git pull 同步远程代码？(Y/N)
- If Y:
git pull. If conflict, stop and ask for manual resolution.
- Case B:
SYNC:AHEAD- Proceed to Push.
5. Push
- Ask: ✅ Push now? / 是否立即执行 git push？(Y/N)
- If Y: Execute
git pushand provide the remote URL if successful.
What ships with it
1 file 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.
- 1mo ago First seen · 54 lines · 42 tokens per session scan A 8efa92afe2cb
gemit-workflow is a skill published in the GitHub repository znkd/tentacles (2 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 564 once invoked, about $0.0002 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 skills, from other repositories
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
conventional-commits
Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
pr-squash-message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario…
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.