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 agentmods add skills/asdecided/core/decided-importnpx skills add asdecided/core --skill decided-importgit clone --depth 1 https://github.com/asdecided/coreWhat 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 | $0.00098 | $0.01547 |
| Opus 5 | $0.00049 | $0.00773 |
| Sonnet 5 | $0.00020 | $0.00309 |
| Haiku 4.5 | $0.00010 | $0.00155 |
Grade A, and why
decided-import 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RAC single-document import
Reshape one existing document into one valid RAC artifact. You propose; the
human ratifies; decided validate is the deterministic check. This skill never
adds AI to the AsDecided core — it runs in the coding agent and uses the decided CLI.
Hard constraints
- One document in, one artifact out. If asked to import a directory, a
whole wiki, or several documents at once, stop and explain that this skill
handles exactly one document → one artifact by design. For multi-format or
bulk conversion, point the user to the
decided-ingestskill. - The schema is not yours to invent. Read the real shape with
decided schema <type>(anddecided schemafor the list of recognised types). Use the real section names, the real five artifact types, and the real## Related <Type>relationship sections. Never guess or hard-code a field, type, or relationship kind. If you cannot rundecided schema, stop and say so. - Human review is mandatory and explicit (before any file is written).
Present the draft and require the user to confirm or correct (a) the
artifact type, (b) the title, and (c) each relationship before you write
anything. Relationships are suggestions to confirm, never silently
asserted. The
idis minted bydecided new(opaque, system-assigned) — never hand-write or choose it; show it after. - Close on deterministic validation. After writing, run
decided validate. If it fails, show the errors and offer to fix them, then re-validate. Never leave an invalid artifact behind. - No invention. Reformat only what the source says. Do not invent context, consequences, rationale, or requirements. Where a required section has no source material, flag the gap and ask the user — do not fill it with plausible-sounding text.
1. Get the source
Ask the user for the one document — pasted text or a file path — and, if it is not obvious, what kind of decision or requirement it represents. If they offer more than one document or a directory, apply the single-document constraint above before going further.
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.
- 2d ago First seen · 141 lines · 98 tokens per session scan A 8d59e66f8e51
decided-import is a skill published in the GitHub repository asdecided/core (292 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,547 once invoked, about $0.0005 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
project-docs
Software development project documentation management and progress tracking. Use when: (1) Initializing a new software project and need to create all required documentation (MRD, PRD, Technical Plan, Roadmap), (2) Updating project roadmap after completing tasks, (3) Getting a summary of current project progress, (4)…
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
slice-init
Creates an L2 slice in the abapwiki knowledge base: a business process on which to build functional documentation. Writes the manifest (curated anchors + mandatory real owner) and derives the membership from the dependency graph (BFS hop<=2). Use this skill to start the L2 process on a custom domain. Does not promote…
capture-answer
Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.