Borrowing it
Nothing to install: this file belongs to eve0415/cella. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eve0415/cella/main/.claude/skills/cella-ops/SKILL.mdgit clone --depth 1 https://github.com/eve0415/cellaWrote 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/eve0415/cella/cella-ops)<a href="https://agentmods.dev/skills/eve0415/cella/cella-ops"><img src="https://agentmods.dev/badge/skills/eve0415/cella/cella-ops/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/eve0415/cella/cella-ops"><img src="https://agentmods.dev/badge/skills/eve0415/cella/cella-ops.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.00056 | $0.04611 |
| Opus 5.5 | $0.00022 | $0.01844 |
| Sonnet 5.5 | $0.00011 | $0.00922 |
| Haiku 4.5 | $0.00006 | $0.00461 |
Grade A, and why
cella-ops 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 2mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2mo ago First seen · 411 lines · 56 tokens per session scan A 805eea33602e
cella-ops is a skill published in the GitHub repository eve0415/cella (6 stars, last pushed yesterday), licensed GPL-3.0. It adds 56 tokens to every session and 4,611 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
fr-isolation
Run work in an isolated workspace: git worktree + devcontainer, driven through the fr isolation CLI (exec-bridge). Use when feature work must not touch the base repo, when fr-brainstorming or fr-goal needs a workspace, when the operator says "isolate this" / "run it in the container", or to clean up after a merged PR.…
development-environment
IDE setup, dev containers, and local development tools.
pr-track-v1
Create a GitHub tracking issue in Kilo-Org/kilocode that captures a merged Kilo v1 PR's behavior so it can be re-implemented or verified in opencode v2. Use when the user invokes /pr-track-v1 or asks to track a v1 core fix/feature for the v2 rewrite.
kilocode-merge-minimizer
Use when changing shared upstream-owned files to add Kilo-specific behavior, editing kilocodechange markers in shared code, or moving additive behavior out of shared code to reduce upstream merge conflicts. Do not use for changes confined to Kilo-owned paths such as packages/kilo-vscode/ or packages/kilo-ui/.
deploy-akashic
A deployment procedure for an Akashic project that checks and merges an approved pull request, then submits the resulting code revision to update a Docker-based service. The host system handles stopping, moving, and restarting the service.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.