@moda-ai/cli 1.13.2 → 1.13.3

package/dist/harness-report.js

@@ -44,7 +44,10 @@ const HARNESS_REPORT_CITATION_TYPES = new Set([
     'command_output',
     'production_evidence',
 ]);
-const MAX_HARNESS_REPORT_BYTES = 1_500_000;
+// Raised from 1.5 MB to 12 MB so artifacts can carry their full usable content
+// (prompt bodies, tool signatures/docstrings, guardrail rules) for downstream
+// prompt/tool optimization — not just location metadata.
+const MAX_HARNESS_REPORT_BYTES = 12_000_000;
 const MAX_HARNESS_REPORT_CLAIMS = 250;
 const MAX_HARNESS_REPORT_CITATIONS = 400;
 const MAX_HARNESS_REPORT_SUMMARY_LENGTH = 1_200;

package/dist/harness.d.ts

@@ -90,6 +90,14 @@ export interface HarnessArtifact extends HarnessDetection {
     contentHash?: string;
     ownedByAgentId?: string;
     usedByAgentIds: string[];
+    /**
+     * The actual usable content of the artifact, captured so downstream
+     * consumers (prompt optimization, tool optimization) can use it without
+     * re-reading the repo: the full prompt text for `prompt`, the signature +
+     * docstring/description for `tool`, the rule for `guardrail`, the assertion
+     * for `eval`, the config values for `model_config`, etc.
+     */
+    body?: string;
 }
 export interface HarnessIdentityNamespace extends HarnessDetection {
     id: string;

package/dist/harness.js

@@ -1374,6 +1374,7 @@ function renderExternalHarnessAnalystPrompt(options) {
         'Each graph item with evidence must use evidence: [{ path, reason }], not citationIds/citations.',
         'Runtime agents must include id, name, kind:"runtime_agent", root, entrypointIds, channelAdapterIds, artifactIds, identityNamespaceIds, deploymentIds, frameworkIds, modelProviderIds, confidence, evidence.',
         'Artifacts must include id, type, name, scope, usedByAgentIds, confidence, evidence, and optional sourcePath/contentHash/ownedByAgentId. Emit one artifact PER tool, PER prompt (including each inline system prompt), PER guardrail, and PER eval — enumerate them all; artifact types are entrypoint, prompt, tool, skill, eval, retrieval_index, memory, guardrail, model_config, unknown.',
+        'Also set `body` on each artifact to its actual usable content so it can be consumed downstream WITHOUT re-reading the repo: for `prompt` the COMPLETE prompt text verbatim (full inline `instructions=`/system-prompt string or full prompt file); for `tool` the signature (name + parameters + types) and its docstring/description; for `guardrail` the rule/condition; for `eval` what it asserts; for `model_config` the configuration values. Copy the text in full — do not summarize or truncate `body` (it is the artifact we optimize). Redact any secret literals.',
         'For every `prompt` and `tool` artifact, at least one evidence entry MUST pin an exact source location so downstream optimization can retrieve the item text: carry a numeric `line` (the definition line, or the first line of the range) — evidence: [{ path, line, reason }]. The only exception is an artifact whose entire dedicated file is the text (e.g. a standalone prompt file); set its sourcePath and cite that same file and no line is required. When a single file holds multiple inline prompts or tool definitions, give each its own distinct line — a bare { path, reason } is a defect there.',
         'Agent families must include id, name, runtimeAgentIds, sharedArtifactIds, confidence, evidence.',
         'Frameworks/providers must include packageNames and runtimeAgentIds arrays; providers also include envVars and modelHints arrays.',
@@ -1401,6 +1402,7 @@ function renderExternalAnalystProtocol() {
         '- Also emit artifacts for guardrails (type "guardrail"), evals/tests-of-agents (type "eval"), memory/session stores (type "memory"), retrieval indexes (type "retrieval_index"), and model configuration (type "model_config").',
         '- Only runtime AGENTS may be modeled representatively: if the repo is a framework/SDK/examples collection, you need not treat every example as a distinct production agent — but you MUST still enumerate every distinct tool, prompt, guardrail, and eval as its own artifact.',
         '- Each enumerated artifact needs evidence: [{ path, reason }] (file path + short reason); a full line+excerpt citation is required only for the narrative `claims`, NOT for every artifact — so listing hundreds of tools/prompts is cheap and expected.',
+        '- Capture the actual usable content in each artifact\'s `body`: full prompt text for prompts, signature+docstring for tools, the rule for guardrails, the assertion for evals, config values for model configs. This inventory is consumed directly for optimization, so `body` must be the complete text (verbatim, not summarized), with secret literals redacted.',
         '- EXCEPTION — `prompt` and `tool` artifacts MUST pin an exact location: put a numeric `line` on at least one evidence entry (evidence: [{ path, line, reason }]) at the definition line. That structured location is what lets downstream optimization retrieve the exact prompt/tool text; when one file has several inline prompts or tools, each artifact gets its own line. The only case that needs no line is a whole dedicated file whose entire content is the artifact (set sourcePath to that file and cite it). Still no excerpt required — just the line.',
         '- For every runtime agent, read and cite at least one concrete entrypoint or orchestration line, and link its prompts/tools via artifactIds.',
         '- Keep going until every prompt, tool, guardrail, and eval in scope is represented as an artifact. Use unknowns only for genuinely ambiguous items — never to skip enumeration. Respect the hard caps (<=250 claims, <=400 citations): artifacts are uncapped, so when there are many items keep enumerating them as artifacts and reserve claims/citations for the most important ones.',
@@ -2529,13 +2531,17 @@ function maybeAddPromptArtifact(graph, file) {
     if (!isPrompt)
         return;
     const id = stableId('prompt', file.path);
+    const text = file.text ?? readFileSync(file.absPath, 'utf8');
     upsertArtifact(graph, {
         id,
         type: 'prompt',
         name: promptNameFromPath(file.path),
         scope: 'agent',
         sourcePath: file.path,
-        contentHash: hashText(file.text ?? readFileSync(file.absPath, 'utf8')),
+        contentHash: hashText(text),
+        // Capture the full prompt text so downstream prompt optimization can use it
+        // directly without re-reading the repo.
+        body: text,
         usedByAgentIds: [],
         confidence: 0.72,
         evidence: [{ path: file.path, reason: 'Prompt-like file found under prompts directory.' }],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moda-ai/cli",
-  "version": "1.13.2",
+  "version": "1.13.3",
   "description": "CLI for Moda - AI agent analytics and observability",
   "type": "module",
   "bin": {

package/skills/integration/index.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "moda.skill_index.v1",
-  "bundled_at": "2026-07-06T10:32:52.250Z",
-  "cli_version": "1.13.2",
+  "bundled_at": "2026-07-06T18:51:44.915Z",
+  "cli_version": "1.13.3",
   "skills": [
     {
       "id": "integration-node-anthropic",