Borrowing it
Nothing to install: this file belongs to acartine/foolery. 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/acartine/foolery/main/.agents/skills/knots-create/SKILL.mdgit clone --depth 1 https://github.com/acartine/fooleryWrote 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/acartine/foolery/knots-create)<a href="https://agentmods.dev/skills/acartine/foolery/knots-create"><img src="https://agentmods.dev/badge/skills/acartine/foolery/knots-create.svg" alt="Measured on agentmods" 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.00508 |
| Opus 5 | $0.00021 | $0.00254 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
knots-create 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 7d 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
Knots Create
Agent identity
Create or receive a lease before creating the knot:
kno lease create --nickname "<session-name>"
Pass the lease to kno new, notes, and handoff capsules. Authorship for notes
and handoff capsules comes from the bound lease. Without a lease, metadata can
be recorded as [unknown <date>].
Do not copy legacy --*-agentname/model/version identity flags from telemetry
or command history. They are deprecated and ignored by current kno.
Outcome
Create one well-defined knot. Keep the title short and action-oriented. Put the
goal, verification steps, and constraints in -d. Put only numbered
acceptance criteria in --acceptance.
Description format
Write -d with these sections:
Goal:one short paragraph describing the user-visible outcome.Verification:a numbered list of repeatable checks with exact commands or UI actions and the expected result for each step.Constraints:optional non-obvious requirements, exclusions, or scope boundaries.
Write --acceptance as a numbered list of observable outcomes. Reference exact
interfaces when they exist: CLI commands and flags, API routes, file paths,
state names, schema fields, event names, or UI surfaces. Avoid vague criteria
such as "works well", "clean up", or "handle edge cases".
Command
Run:
kno new "<title>" -d $'Goal:\n<goal>\n\nVerification:\n1. <step>\n2. <step>' \
--acceptance $'1. <criterion>\n2. <criterion>' \
--lease <lease-id>
If verification is not yet repeatable, make that gap explicit in the knot so the agent can close it as part of the work.
Then attach a handoff capsule for the agent who will claim the knot:
kno update <id> -H "<capsule>" --lease <lease-id>
The capsule should include the key context, constraints, and verification notes that are not obvious from the title and acceptance criteria.
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.
- 7d ago First seen · 68 lines · 42 tokens per session scan A 4d2a34d44a42
knots-create is a skill published in the GitHub repository acartine/foolery (54 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 508 once invoked, about $0.0002 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
flow-state
Use when a Flow request reads, mutates, reconciles, completes, archives, or recovers Markdown lifecycle state and transaction journals.
flow-execution
Use when implementing Flow tasks from local task files under .agents/bundles/specs/ /tasks/, claiming ready work, applying the declared verification strategy, recording task notes, committing, and updating task file state.
flow-completion
Use when reviewing, finishing, archiving, reverting, validating, documenting, or cleaning up Flow work after implementation or phase completion.
flow-sync-status
Use when reconciling Flow task truth into a spec, displaying status queues, refreshing project context, or checking bundle state anomalies.
work-beads
Work the project's Beads task queue end-to-end - claim a bead, build in an isolated worktree, verify, review, merge, close, report. Use when the user says "/work-beads", "/work-beads 5", "work the next N beads", "work on ", "pick up some open tasks", or asks to work the backlog. Applies to every coding agent (Claude…
file-todos
Manage file-based todos in todos/ directory. Use when creating, triaging, or tracking todos and integrating them with code review.