Borrowing it
Nothing to install: this file belongs to typedef-ai/fenic. 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/typedef-ai/fenic/main/.claude/skills/update-fenic-skill/SKILL.mdgit clone --depth 1 https://github.com/typedef-ai/fenicWrote 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/typedef-ai/fenic/update-fenic-skill)<a href="https://agentmods.dev/skills/typedef-ai/fenic/update-fenic-skill"><img src="https://agentmods.dev/badge/skills/typedef-ai/fenic/update-fenic-skill/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/typedef-ai/fenic/update-fenic-skill"><img src="https://agentmods.dev/badge/skills/typedef-ai/fenic/update-fenic-skill.svg" alt="Reviewed on agentmods" width="80" 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 Agent Snooping · line 25 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00074 | $0.00857 |
| Opus 5 | $0.00037 | $0.00428 |
| Sonnet 5 | $0.00015 | $0.00171 |
| Haiku 4.5 | $0.00007 | $0.00086 |
Grade A, and why
update-fenic-skill 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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update the fenic-mechanics skill for a new fenic version
The fenic-mechanics skill is hybrid: a generated reference
(.claude/skills/fenic-mechanics/reference/*.md, introspected from the installed
fenic — never edit by hand) plus hand-authored judgment (SKILL.md,
gotchas.md — the namespace law, calling conventions, and silent traps). When
fenic changes version, regenerate the first and re-review the second.
Procedure
-
Confirm the installed version changed.
uv run --project . python -c "from importlib import metadata; print(metadata.version('fenic'))" cat .claude/skills/fenic-mechanics/reference/VERSION -
Regenerate the reference (deterministic — only real API changes will diff):
uv run --project . python .claude/skills/fenic-mechanics/scripts/generate_reference.py -
Inspect the API deltas:
git diff --stat .claude/skills/fenic-mechanics/reference/ git diff .claude/skills/fenic-mechanics/reference/Classify each change: added symbol, removed symbol, renamed symbol, or changed signature (param added/removed/renamed/retyped).
-
Re-review the hand-authored judgment against the deltas. Update
SKILL.md/gotchas.mdonly where a delta touches them:- Namespace/import law — did any namespace move, or did a function become
a method (or vice-versa)? (e.g. something leaving/entering
fc.arr,fc.dt,fc.semantic). - The 4 silent traps — re-verify each still holds:
fc.json.jqstill returnsArrayType(JsonType); semantic templates still Jinja2{{ }};fc.dt.datediff(end, start)arg order;fc.dt.to_timestampformat dialect. A changed signature on any of these is high-priority. - Model/config — provider classes,
input_tpm/output_tpmvstpm,default_*requirements. - The "wrote X, meant Y" table — drop rows whose anti-pattern is now impossible, and add rows for new traps the signature changes introduce.
- Namespace/import law — did any namespace move, or did a function become
a method (or vice-versa)? (e.g. something leaving/entering
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.
- 11d ago First seen · 76 lines · 74 tokens per session scan A 6c7cc82b2ad8
update-fenic-skill is a skill published in the GitHub repository typedef-ai/fenic (672 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 857 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
research
Run deep research on any topic using the Deep Research MCP server. Use this skill whenever the user wants to research a topic, gather information, find sources, or create a research document. Triggers on: 'research this', 'find out about', 'gather information on', 'I need to understand', 'deep dive into', or any…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
run_jinx
Execute a jinx by name (already loaded on the team) or by filesystem path (e.g. a freshly createdjinx that isn't yet registered), passing input values as a JSON object. Returns the jinx's output field or the full context dict. Use this to run a jinx you just wrote without exiting the session.