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 jentic/jentic-one --skill init-designgit clone --depth 1 https://github.com/jentic/jentic-oneWrote 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/jentic/jentic-one/init-design)<a href="https://agentmods.dev/skills/jentic/jentic-one/init-design"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/init-design/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/jentic/jentic-one/init-design"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/init-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01416 |
| Opus 5.5 | $0.00000 | $0.00566 |
| Sonnet 5.5 | $0.00000 | $0.00283 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
init-design 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 27d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: init-design
Set up and carry out a new design in docs/design/designs/<name>/. Follows the conventions established in platform-actors — a brief README index, problem statement, scope, architecture decisions, open questions, and per-concern sub-documents. Ends with scaffolded stubs for each planned document.
Trigger
Invoked when the user asks to start a design for a new feature, module, or cross-cutting concern. Examples:
- "start a design for X"
- "set up the design docs for X"
- "run init-design on X"
Steps
1. Clarify scope (ask the user)
Before writing anything, ask two questions in a single message:
a. Pull in related context? Should I scan the repo for existing code, specs, or design docs relevant to
<feature>? (Relevant modules, OpenAPI specs, existing ORM models, etc.) This shapes the problem statement and identifies constraints before you commit to an approach.b. Documents to create? Besides README.md, which concern-level docs do you want scaffolded now? Suggest a default list based on the feature — the platform-actors design used:
actors.md,access-scenarios.md,endpoints.md,openapi-sketch.yaml, per-actor subdirs (each withREADME.md,auth.md,endpoints.md),authorization-server/. Say which you want, or say "suggest" and I'll propose a list with rationale.
Wait for the user's answers before proceeding.
2. Pull in related context (if yes)
Search for:
- Existing source modules that the feature touches (grep for the feature noun in
src/,openapi/) - Existing design docs that mention the feature or its entities
- OpenAPI specs that will need extending
- ORM models and migrations relevant to the new entities
- Existing permission scopes in
admin/core/permissions.py
Summarise findings in a short bullet list to the user before writing any docs. This becomes the raw material for the "Relationship to existing work" section of the README.
3. Write the README
docs/design/designs/<name>/README.md — the index and anchor doc for the design. Structure:
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.
- 27d ago Changed · -4 lines 574d54ee2674
- 1mo ago First seen · 144 lines · 0 tokens per session scan A 625324d59e2c
init-design is a skill published in the GitHub repository jentic/jentic-one (190 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,416 tokens. 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
lobu-operator
Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.
company-agent-infrastructure
Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…
lobu-builder
Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…
crm-ops
How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.
deliveroo-order
Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…
lobu
Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.