<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/agents/scaffolder.md, branch bump/cloud-sql-sqlserver</title>
<subtitle>Official Claude Code plugin directory
</subtitle>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/'/>
<entry>
<title>code-modernization: simpler commands, a source option, a report page and an equivalence check</title>
<updated>2026-09-25T03:14:51+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:14:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=cafefb304bde4070c6c0877528ee49c1252eff85'/>
<id>cafefb304bde4070c6c0877528ee49c1252eff85</id>
<content type='text'>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: second-order injection fencing, path guards, scoped scaffolder agent</title>
<updated>2026-06-09T19:40:58+00:00</updated>
<author>
<name>Morgan Westlee Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-09T19:40:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d44da811468a8124135a67ba64a3d0257a2e36b6'/>
<id>d44da811468a8124135a67ba64a3d0257a2e36b6</id>
<content type='text'>
Addresses automated security review of the workflow conversion:

- Agent-produced text (rule specs, finding descriptions, dedup lists) is
  fenced as untrusted data when interpolated into downstream agent prompts,
  with embedded fence markers stripped so the fence can't be escaped;
  referees and judges are told to re-derive claims from the cited code.
- system/service/subdir names that land in filesystem paths inside prompts
  are validated against a strict pattern — traversal-shaped values throw
  before any agent spawns.
- Reimagine scaffolding now uses a dedicated 'scaffolder' agent with an
  explicit minimal tool list, a single-directory write scope, and the
  untrusted-content discipline extended to the generated spec/architecture
  docs it builds from (they derive from untrusted legacy code).

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Addresses automated security review of the workflow conversion:

- Agent-produced text (rule specs, finding descriptions, dedup lists) is
  fenced as untrusted data when interpolated into downstream agent prompts,
  with embedded fence markers stripped so the fence can't be escaped;
  referees and judges are told to re-derive claims from the cited code.
- system/service/subdir names that land in filesystem paths inside prompts
  are validated against a strict pattern — traversal-shaped values throw
  before any agent spawns.
- Reimagine scaffolding now uses a dedicated 'scaffolder' agent with an
  explicit minimal tool list, a single-directory write scope, and the
  untrusted-content discipline extended to the generated spec/architecture
  docs it builds from (they derive from untrusted legacy code).

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
