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 LucasSantana-Dev/sharekit --skill plangit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/plan)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/plan"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/plan/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/lucassantana-dev/sharekit/plan"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/plan.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.00101 | $0.01020 |
| Opus 5.5 | $0.00040 | $0.00408 |
| Sonnet 5.5 | $0.00020 | $0.00204 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
plan 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan
Use planning only when it actually reduces risk.
Steps
- Read local guidance and active handoff.
- Pull only the context needed for the task.
- State goal, in-scope, and out-of-scope.
- Break work into short phases.
- Give each phase exact file paths (Files Touched) and a runnable Verify command — agents execute paths and commands, not prose.
- Write the plan to
.claude/plans/or.agents/plans/.
Rules
- Keep phases small enough to finish without drifting.
- Note what would cause replanning.
- If work is already partly done, document the current state before planning the rest.
- Prefer the provided plan template (
references/plan-template.md). - Don't over-specify: too much detail buries priorities. File paths, scope, verification — then stop.
- AC contract (team/product work): when a spec exists in
specs/, every task must carry its requirement ID (REQ-n) and the EARS acceptance criteria (AC-x.y, GIVEN/WHEN/THEN) that prove it done — the AC-coverage gate (hooks/check-ac-coverage.sh) fails untraceable tasks. Acceptance criteria map 1:1 to eval tasks where an eval suite exists. - Spec-anchored: extend the existing spec for a feature rather than creating a new one (
specs/<feature>/; template atspecs/_template/). The spec directory, not personal memory, is the cross-operator source of truth.
Extend vs new plan
Before writing, scan .claude/plans/ and .agents/plans/:
- Existing plan covers same scope AND ≤30 days old → extend (append phases, edit status header, keep history).
- Same scope but >30 days old → new plan; mark old as superseded.
- Different scope → new plan.
When extending, update the status header to reflect partial completion (e.g. "Phases 1-5 done; Phases 6-8 added 2026-05-14").
Parallel execution
If the plan's tasks will fan out to ≥2 parallel agents, the executor is /parallel-phases and it ingests a task-level schema (### T1 blocks with specialist/model/scope_in/scope_out/depends_on/acceptance — see parallel-phases/references/plan-format.md). Write sequential plans with this skill's template; write fan-out plans directly in that schema.
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 · 81 lines · 101 tokens per session scan A 3d8ed8c525a9
plan is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,020 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.