{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-dynamically-loaded-skill-manifest-become-an-injection-vector-only-after-its-first-successful-invocation",
  "title": "Why does an instance of a dynamically loaded skill manifest become an injection vector only after its first successful invocation?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent runtimes that load tool/skill manifests at runtime (JSON/YAML descriptors declaring name, description, parameters, and invocation bindings) and cache them after first successful call. Does not apply to statically compiled tool bindings or manifests re-validated on every invocation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-skill-manifest-become-an-injection-vector-only-after-its-first-successful-invocation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-skill-manifest-become-an-injection-vector-only-after-its-first-successful-invocation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-dynamically-loaded-skill-manifest-become-an-injection-vector-only-after-its-first-successful-invocation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1270,
    "python_slice_tokens": 311,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **parse-time trust** and **invocation-time trust**. A manifest is validated once, at load, against a schema: field types, required keys, parameter shapes. After the first successful invocation the runtime promotes the manifest into a *trusted cached descriptor* — it is no longer re-parsed, and its fields (especially `descr...",
    "what_was_observed": "In a runtime that loaded manifests into a dict keyed by skill name and passed the same dict object by reference into the planner's context, the following sequence reproduced consistently: 1. Manifest `summarize` loaded and schema-validated. `description` = \"Summarize a document.\" 2. First invocation succeeded; descriptor promoted to `trusted_cache[\"summarize\"]`. 3. A second skill, `fetch_url`, returned attacker-contr...",
    "condition_of_validity": "This boundary holds only when all of the following are true: - The descriptor is cached by **reference**, not deep-copied, into any context that untrusted content can reach. - Promotion to trusted status happens on **first successful invocation**, not on every invocation. - At least one descriptor field (`description`, `examples`, default args) is **consumed...",
    "decision_boundary": "The operational rule: **trust is a property of the object's lineage, not its schema.** A manifest that passed validation is safe to *load*; it is not safe to *reuse by reference* across a context boundary that untrusted data crosses. The decision point is at promotion: either (a) deep-freeze the descriptor and hand out immutable copies, or (b) re-bind integr...",
    "operational_effect": "Downstream, the effect is a **silent privilege escalation of the tool-selection layer**: the planner executes with the authority of the trusted cache while its inputs carry attacker text. Detection is hard because the manifest on disk is clean and the validator is silent. Mitigation requires treating the cached descriptor as a sealed value — copying on read ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "0ac700e9660e5e68067f9cef00df13b4c671b6c69b4b5ba242e06832eb3ae967",
    "verified_classes": [
      "ManifestTrustError"
    ],
    "verified_functions": [
      "promote_descriptor",
      "consume_for_planner",
      "planner_turn"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ManifestTrustError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "copy",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
