agentsclimarketplace

Amadeus security patch

Skill amadeus-dlc/amadeus/.kimi-code/skills/amadeus-security-patch

Agent skills, templates, examples, validators, and docs for operating Amadeus DLC, a lifecycle contract for AI driven software development.

Install
npx -y skills add amadeus-dlc/amadeus --skill amadeus-security-patch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the AI-DLC workflow with the security-patch scope baked in — no scope detection. CVE response. Packaging over `/amadeus --scope security-patch`, which works without this skill.

SKILL.md

1.6 KB, 328 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC — security-patch scope

Drive the AI-DLC engine with the security-patch scope fixed. This is the same deterministic forwarding loop the /amadeus orchestrator runs, with --scope security-patch baked into the first next so scope detection is skipped. The engine owns all routing; the conductor persona arrives on the first directive's conductor_persona field — adopt it for the whole run.

The loop

  1. directive = bun .kimi-code/tools/amadeus-orchestrate.ts next --scope security-patch $ARGUMENTS
  2. Act on directive.kind exactly as the orchestrator does (run-stage / ask / print / error / done) — see amadeus-common/protocols/stage-protocol.md.
  3. bun .kimi-code/tools/amadeus-orchestrate.ts report --stage <directive.stage> --result <outcome> [--user-input "<text>"] when the directive names a stage; omit --stage only for non-stage report round-trips.
  4. Repeat from step 1 until directive.kind == done.

Pass $ARGUMENTS through verbatim after --scope security-patch; the engine parses any flags (--status, --stage, …) and the --scope from the state file always wins on an existing workflow, so re-running a started workflow resumes it. To run a different scope, use /amadeus --scope <other> instead.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.