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 izkreny/agentifico --skill implementgit clone --depth 1 https://github.com/izkreny/agentificoWrote 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/izkreny/agentifico/implement)<a href="https://agentmods.dev/skills/izkreny/agentifico/implement"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/implement/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/izkreny/agentifico/implement"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/implement.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.00114 | $0.02178 |
| Opus 5.5 | $0.00046 | $0.00871 |
| Sonnet 5.5 | $0.00023 | $0.00436 |
| Haiku 4.5 | $0.00011 | $0.00218 |
Grade A, and why
implement 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 18d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tools used: bare
Bashrather than a narrowed list, because this is the one skill in the flow that runs the repository's own commands - tests, linters, builds - and those cannot be enumerated here;ghandgitcarry the PR and branch work inside it.Read/Write/Edit/Grep/Globcarry the code itself;TodoWritemirrors the plan's## Stepsinto the session todo list during implementation;EnterWorktreemoves the session into the branch's worktree where the owner keeps one.
The user invoked this skill with the argument: $ARGUMENTS
This is a routing skill. Read $ARGUMENTS, pick exactly one workflow per Routing, and follow it inline, in this session.
Implementation runs in the session that holds the context for it. That session has read the plan, or has heard which findings the owner said stand, and it knows why the code is shaped as it is. It will not undo something deliberate the way a cold agent does, and it does not have to be told in a prompt what it already knows. Never hand this work to a subagent, and never summarise a workflow's handoff: the handoff is the record, and it is printed as the workflow wrote it.
Settling the plan record is the first act of workflows/implement.md Step 1 rather than something done before starting, because there is no before. A fix never does it: the review protocol in the pr-flow skill owns that state, unpushed.
All paths below are relative to this skill's own directory. Resolve them against wherever this skill is installed rather than assuming a location.
Every file here is written to the agent, so you is the agent reading it. The human is the owner, always in the third person - the same voice rule as pr-flow, and for the same reason. The exception is README.md, which the owner reads rendered and which addresses them directly.
Where this sits
This skill is the implementation stage of a branch's life, the node the pr-flow and tracker lifecycle diagrams name implement. Everything around it stays there: open created the draft PR this skill requires, ready audits what this skill leaves behind, review and merge come later. You never do their work from here - never lift the draft, never post a review, never merge.
It is also written to be resumable across sessions: all state lives on the PR and the branch - ticked boxes, commits - and none in the session. A fresh session picks up mid-implementation by reading that state, which is what workflows/implement.md Step 2 does.
What ships with it
3 files 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.
- 18d ago Changed 8b787f1b1999
- 21d ago Changed · +11 lines 1266dc8a5709
- 1mo ago Changed · -1 lines 1d9fe2431fad
- 1mo ago First seen · 59 lines · 114 tokens per session scan A f56b581a96d2
implement is a skill published in the GitHub repository izkreny/agentifico (2 stars, last pushed 11d ago), licensed MIT. It adds 114 tokens to every session and 2,178 once invoked, about $0.0005 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.