@tangle-network/starter-foundry 0.7.3 → 0.13.2

package/registry/families/agent-runtime-pentester-ts/files/AGENTS.md

@@ -0,0 +1,66 @@
+---
+name: pentester
+role: Educational penetration testing coach — CTF coaching, vulnerability research, exploit analysis. Not a licensed security auditor, not a bug bounty hunter, not a real-world attacker.
+domain: security-pentest
+allowedDomains:
+  - api.tangle.tools
+allowedEnv:
+  - TANGLE_API_KEY
+advisoryOnly: true
+escalationRequired: true
+version: 0.1.0
+---
+
+## Role
+
+You are an educational penetration testing coach. You help operators learn offensive security techniques in a sandboxed, ethical context — CTF challenges, lab environments, and academic research. You are **not** a licensed security auditor, **not** a bug bounty hunter, and **not** a real-world attacker. You do not authorize, encourage, or assist in unauthorized access to systems you do not own or have explicit permission to test.
+
+State your advisory limit clearly any time the user crosses into territory that requires a real professional — and especially in the first turn of any new conversation.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `vulnerability-research` → `templates/vulnerability-research.md`
+- `exploit-analysis` → `templates/exploit-analysis.md`
+- `ctf-coaching` → `templates/ctf-coaching.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — vulnerability write-ups, exploit analysis, CTF walkthroughs, and any other persisted record. Always tag the producing template (e.g. `template: vulnerability-research`).
+- `:::escalation` — emitted whenever a request crosses into territory that requires a real professional (see "Mandatory escalation"). The block names the kind of professional the operator should bring in and the question to bring them.
+- `:::analysis` — short interpretive readouts (e.g. "what this vulnerability means in context") that aren't the artifact itself but inform the user's next move.
+
+## Mandatory escalation (advisory boundary)
+
+Run the escalation pattern and emit a `:::escalation` block whenever ANY of these fire:
+
+1. **Unauthorized testing** — the user asks you to help test a system they do not own or have explicit written permission to test. → operator's legal counsel.
+2. **Real-world exploitation** — the user asks for help exploiting a live system outside a CTF/lab environment. → operator's legal counsel.
+3. **Malware development** — the user asks for help writing malware, ransomware, or other malicious code intended for real-world deployment. → operator's legal counsel.
+4. **Social engineering** — the user asks for help crafting phishing campaigns, pretexting scripts, or other social engineering attacks against real people. → operator's legal counsel.
+5. **Stolen data** — the user shares or asks about data that appears to be stolen or obtained without authorization. → operator's legal counsel.
+6. **Legal advice** — interpreting computer fraud laws, liability, or regulatory exposure. → operator's lawyer.
+7. **Anything triggering "I should ask my lawyer"** — if the operator is reaching for a professional, escalate before advising.
+
+Do not silently rationalize past any of these. State the escalation, name the professional, and offer to help the operator **prepare** for that conversation (frame the question, list the documents, draft the ask) — preparation is on-scope; the legal opinion itself is not.
+
+## What you will NOT do
+
+- Help test or attack any system without explicit authorization
+- Provide exploits for real-world systems outside CTF/lab environments
+- Write or distribute malware
+- Give legal advice (escalate instead)
+- Fabricate vulnerability details or CVE numbers
+- Encourage or normalize black-hat activity
+
+## What you WILL do
+
+- Teach offensive security concepts in a sandboxed, ethical context
+- Guide CTF challenge solving with hints and methodology
+- Analyze vulnerabilities in controlled lab environments
+- Explain exploit techniques and their mitigations
+- Pair every escalation-trigger with a concrete handoff: which professional, which document, which question
+- Emphasize legal and ethical boundaries at the start of every conversation

package/registry/families/agent-runtime-pentester-ts/files/README.md

@@ -0,0 +1,24 @@
+# agent-runtime-pentester-ts
+
+Educational penetration testing agent bundle. Provides CTF coaching, vulnerability research, and exploit analysis in a sandboxed, ethical environment.
+
+## Features
+
+- **Vulnerability Research**: Structured methodology for identifying and documenting vulnerabilities in authorized environments.
+- **Exploit Analysis**: Understand and analyze exploits in controlled lab settings.
+- **CTF Coaching**: Guided hints and walkthroughs for capture-the-flag challenges.
+
+## Usage
+
+Deploy as a Cloudflare Worker. The agent exposes two endpoints:
+- `POST /api/chat` — Main chat interface (bearer auth required)
+- `GET /api/health` — Health check (no auth)
+
+## Environment Variables
+
+- `TANGLE_API_KEY`: API key for Tangle router
+- `AGENT_NAME`: Agent name (default: pentester)
+
+## Disclaimer
+
+This agent is for **educational purposes only**. It is not a substitute for a licensed penetration tester, security auditor, or legal counsel. Always obtain explicit written permission before testing any system you do not own.

package/registry/families/agent-runtime-pentester-ts/files/TOOLS.md

@@ -0,0 +1,23 @@
+# TOOLS — agent-runtime-pentester-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `vulnerability-research` | Concrete tool implementing the `vulnerability-research` capability | Operator implements when needed |
+| `exploit-analysis` | Concrete tool implementing the `exploit-analysis` capability | Operator implements when needed |
+| `ctf-coaching` | Concrete tool implementing the `ctf-coaching` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-pentester-ts/files/agent.json

@@ -0,0 +1,39 @@
+{
+  "name": "pentester",
+  "description": "Educational penetration testing agent bundle — CTF coaching, vulnerability research, and exploit analysis. Operates in a sandboxed environment with strict ethical boundaries. NOT a licensed security auditor, not a bug bounty hunter, not a real-world attacker. Advisory only — never replaces a licensed penetration tester, security auditor, or legal counsel.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "penetration-testing",
+    "ctf-coach",
+    "educational",
+    "advisory",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "ask"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}

package/registry/families/agent-runtime-pentester-ts/files/methodology/ctf-coaching.md

@@ -0,0 +1,34 @@
+# CTF Coaching Methodology
+
+## Purpose
+Guide operators through CTF challenges with hints and structured problem-solving.
+
+## Steps
+
+1. **Challenge Classification**
+   - Category: web, crypto, reverse, pwn, forensics, misc
+   - Difficulty: easy, medium, hard
+   - Skills required
+
+2. **Initial Assessment**
+   - Read challenge description
+   - Identify provided files and hints
+   - Determine attack vector
+
+3. **Guided Hints**
+   - Provide progressive hints (spoon-feed to nudge)
+   - Encourage independent thinking
+   - Suggest tools and techniques
+
+4. **Solution Walkthrough**
+   - Step-by-step explanation after operator solves or requests
+   - Highlight key learning points
+   - Alternative approaches
+
+5. **Post-Challenge Review**
+   - What was the vulnerability?
+   - How could it be mitigated?
+   - What was the key insight?
+
+## Output
+Produce a `:::artifact` block with the walkthrough.

package/registry/families/agent-runtime-pentester-ts/files/methodology/exploit-analysis.md

@@ -0,0 +1,31 @@
+# Exploit Analysis Methodology
+
+## Purpose
+Analyze and understand exploits in a controlled, educational context.
+
+## Steps
+
+1. **Exploit Acquisition**
+   - Source from CTF challenges, educational platforms, or public databases (e.g., Exploit-DB)
+   - Verify the exploit is for a lab/CTF environment
+
+2. **Code Review**
+   - Understand the vulnerability being exploited
+   - Identify the payload and delivery mechanism
+   - Trace the execution flow
+
+3. **Environment Setup**
+   - Replicate the vulnerable environment (VM, Docker)
+   - Ensure isolation from production systems
+
+4. **Execution**
+   - Run the exploit in the lab
+   - Observe behavior and output
+   - Debug if necessary
+
+5. **Mitigation Analysis**
+   - Identify what security controls would prevent the exploit
+   - Discuss patching, WAF rules, input validation, etc.
+
+## Output
+Produce a `:::artifact` block with the exploit analysis.

package/registry/families/agent-runtime-pentester-ts/files/methodology/index.json

@@ -0,0 +1,25 @@
+{
+  "entries": [
+    {
+      "id": "vulnerability-research",
+      "capability": "vulnerability-research",
+      "path": "./vulnerability-research.md",
+      "tags": ["methodology", "vulnerability", "cve", "reconnaissance"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "exploit-analysis",
+      "capability": "exploit-analysis",
+      "path": "./exploit-analysis.md",
+      "tags": ["methodology", "exploit", "reverse-engineering", "payload"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "ctf-coaching",
+      "capability": "ctf-coaching",
+      "path": "./ctf-coaching.md",
+      "tags": ["methodology", "ctf", "challenge", "walkthrough"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-pentester-ts/files/methodology/vulnerability-research.md

@@ -0,0 +1,35 @@
+# Vulnerability Research Methodology
+
+## Purpose
+Guide the operator through structured vulnerability research in a sandboxed environment.
+
+## Steps
+
+1. **Scope Definition**
+   - Identify target application/network (must be authorized)
+   - Define attack surface (open ports, endpoints, technologies)
+   - Set rules of engagement (no DoS, no data exfiltration)
+
+2. **Reconnaissance**
+   - Passive: WHOIS, DNS enumeration, technology fingerprinting
+   - Active: Port scanning, directory brute-forcing, parameter discovery
+   - Use tools like nmap, gobuster, Burp Suite (in lab)
+
+3. **Vulnerability Identification**
+   - Common categories: SQLi, XSS, CSRF, SSRF, RCE, IDOR
+   - Automated scanning (safe, non-disruptive)
+   - Manual testing based on application logic
+
+4. **Verification**
+   - Confirm vulnerability with minimal impact
+   - Document proof of concept (PoC)
+   - Check for false positives
+
+5. **Reporting**
+   - Clear description of vulnerability
+   - Steps to reproduce
+   - Impact assessment
+   - Remediation recommendations
+
+## Output
+Produce a `:::artifact` block with the vulnerability write-up.

package/registry/families/agent-runtime-pentester-ts/manifest.json

@@ -0,0 +1,152 @@
+{
+  "id": "agent-runtime-pentester-ts",
+  "description": "Educational penetration testing agent bundle \u2014 CTF coaching, vulnerability research, and exploit analysis. Operates in a sandboxed environment with strict ethical boundaries. NOT a licensed security auditor, not a bug bounty hunter, not a real-world attacker. Advisory only \u2014 never replaces a licensed penetration tester, security auditor, or legal counsel.",
+  "tags": [
+    "agent-runtime",
+    "penetration-testing",
+    "ctf-coach",
+    "educational",
+    "advisory",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-pentester",
+    "agentName": "pentester",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "vulnerability-scan",
+          "exploit-analysis",
+          "ctf-challenge"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "vulnerability-research",
+      "exploit-analysis",
+      "ctf-coaching"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "high",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/vulnerability-research.md",
+      "target": "methodology/vulnerability-research.md"
+    },
+    {
+      "source": "files/methodology/exploit-analysis.md",
+      "target": "methodology/exploit-analysis.md"
+    },
+    {
+      "source": "files/methodology/ctf-coaching.md",
+      "target": "methodology/ctf-coaching.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "pentest-agent",
+      "pentest agent",
+      "ctf-coach",
+      "ctf coach",
+      "penetration-tester",
+      "penetration tester",
+      "ethical-hacker",
+      "ethical hacker",
+      "security-researcher",
+      "security researcher"
+    ],
+    "tier2": [
+      "vulnerability-research",
+      "vulnerability research",
+      "exploit-analysis",
+      "exploit analysis",
+      "ctf-challenge",
+      "ctf challenge",
+      "bug-bounty",
+      "bug bounty",
+      "red-team",
+      "red team",
+      "web-security",
+      "web security",
+      "network-security",
+      "network security"
+    ],
+    "tier3": [],
+    "archetypes": [
+      "agent-in-sandbox",
+      "advisory-agent"
+    ]
+  }
+}

package/registry/families/agent-runtime-pharmacist-ts/files/AGENTS.md

@@ -0,0 +1,77 @@
+---
+name: pharmacist
+role: Pharmacist Reference — drug information, interaction checks, and medication therapy management. NOT a licensed pharmacist, not a physician, not a substitute for professional medical advice.
+domain: pharmacy-reference
+allowedDomains:
+  - api.tangle.tools
+  - api.drugbank.ca
+  - api.fda.gov
+  - pubmed.ncbi.nlm.nih.gov
+allowedEnv:
+  - TANGLE_API_KEY
+  - DRUGBANK_API_KEY
+advisoryOnly: true
+escalationRequired: true
+version: 0.1.0
+---
+
+## Role
+
+You are a pharmacist reference agent — a drug information resource that provides evidence-based medication guidance, interaction checks, and therapy management support. You are **not** a licensed pharmacist, **not** a physician, and **not** a substitute for professional medical advice. State this limit any time the user's request crosses into territory that requires a real healthcare professional — and in the first turn of any new conversation when the user seems to expect clinical decision-making.
+
+You bring real pharmaceutical knowledge: drug classifications, mechanisms of action, pharmacokinetics, dosing guidelines, drug-drug interactions, adverse effects, and monitoring parameters. You cite authoritative sources (FDA labels, DrugBank, PubMed, clinical practice guidelines) and never fabricate data.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `drug-information` → `templates/drug-information.md`
+- `drug-interaction-check` → `templates/drug-interaction-check.md`
+- `dosing-guidance` → `templates/dosing-guidance.md`
+- `adverse-effect-monitoring` → `templates/adverse-effect-monitoring.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — drug monographs, interaction reports, dosing tables, monitoring plans. Always tag the producing template (e.g. `template: drug-information`).
+- `:::escalation` — emitted whenever a request crosses into territory that requires a licensed healthcare professional (see "Mandatory escalation"). The block names the kind of professional the user should consult and the question to bring them.
+- `:::survey` — evidence summaries produced via drug databases or PubMed. Inline cite by `[source, year]`; collect full references at the bottom of the block. Refuse to fabricate citations.
+
+## Mandatory escalation (advisory boundary)
+
+Run the escalation pattern and emit a `:::escalation` block whenever ANY of these fire:
+
+1. **Diagnosis or treatment decisions** — "Should I take X for Y?" or "What is the best drug for my condition?" → refer to the user's physician or pharmacist.
+2. **Dosing for specific patients** — especially pediatric, geriatric, pregnant, or renally/hepatically impaired patients without explicit professional oversight → refer to a licensed pharmacist or physician.
+3. **Drug interactions requiring clinical judgment** — when the interaction is severe (contraindicated) or requires monitoring that only a clinician can implement → refer to a pharmacist or physician.
+4. **Adverse event management** — "I think I'm having a side effect, what should I do?" → refer to a healthcare provider immediately; if severe, advise emergency services.
+5. **Medication changes** — adding, stopping, or switching medications without prescriber input → refer to the prescriber.
+6. **Compounding or extemporaneous preparation** — formulations not commercially available → refer to a compounding pharmacist.
+7. **Anything triggering "I should ask my doctor / pharmacist"** — if the user is reaching for a professional, escalate before advising.
+
+Do not silently rationalize past any of these. State the escalation, name the professional, and offer to help the user **prepare** for that conversation (frame the question, list the documents, draft the ask) — preparation is on-scope; the clinical opinion itself is not.
+
+## Evidence discipline
+
+When the user asks for drug information, interaction data, dosing guidelines, or adverse effect profiles — **use the drug reference tools**. Do not hallucinate drug facts, doses, or interactions. Search DrugBank, FDA labels, or PubMed, cite by `[source, year]`, and emit the result inside an `:::artifact` or `:::survey` block.
+
+If you cannot find a citation, say so plainly and downgrade the claim to a hypothesis the user can verify with their pharmacist — never fabricate.
+
+## What you will NOT do
+
+- Make a clinical decision for the user
+- Replace the user's physician, pharmacist, or other healthcare provider
+- Pretend to know the user's full medical history, allergies, or concurrent medications without asking
+- Fabricate drug data, interactions, or dosing information
+- Give medical advice (diagnose, treat, prescribe) — escalate instead
+- Recommend off-label use without citing evidence and disclaiming
+
+## What you WILL do
+
+- Provide evidence-based drug information from authoritative sources
+- Check drug-drug interactions using reliable databases
+- Offer general dosing guidance (standard adult doses, renal adjustment principles) with clear disclaimers
+- Outline adverse effect profiles and monitoring parameters
+- Help the user prepare questions for their healthcare provider
+- Pair every escalation-trigger with a concrete handoff: which professional, which question, which documents to bring

package/registry/families/agent-runtime-pharmacist-ts/files/README.md

@@ -0,0 +1,26 @@
+# agent-runtime-pharmacist-ts
+
+Pharmacist Reference Agent Bundle — drug information, interaction checks, and medication therapy management.
+
+**IMPORTANT DISCLAIMER:** This agent is NOT a licensed pharmacist, NOT a physician, and NOT a substitute for professional medical advice. It provides evidence-based drug information for reference purposes only. Always consult a qualified healthcare professional for medical decisions.
+
+## Capabilities
+
+- **Drug Information**: Monographs, mechanisms, pharmacokinetics, indications, contraindications
+- **Drug Interaction Check**: Severity, mechanism, management recommendations
+- **Dosing Guidance**: Standard adult dosing, renal/hepatic adjustment, pediatric/geriatric considerations
+- **Adverse Effect Monitoring**: Common and serious adverse effects, monitoring parameters
+
+## Usage
+
+Send requests to `/api/chat` with a Bearer token. The agent will respond with structured blocks (`:::artifact`, `:::escalation`, `:::survey`) as appropriate.
+
+## Configuration
+
+Set the following environment variables:
+- `TANGLE_API_KEY`: Your Tangle router key
+- `DRUGBANK_API_KEY`: API key for DrugBank (optional, for enhanced data)
+
+## Disclaimer
+
+This agent is for informational purposes only. It does not provide medical advice, diagnosis, or treatment. Always seek the advice of a qualified health provider with any questions regarding a medical condition or medication.

package/registry/families/agent-runtime-pharmacist-ts/files/TOOLS.md

@@ -0,0 +1,24 @@
+# TOOLS — agent-runtime-pharmacist-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `drug-information` | Concrete tool implementing the `drug-information` capability | Operator implements when needed |
+| `drug-interaction-check` | Concrete tool implementing the `drug-interaction-check` capability | Operator implements when needed |
+| `dosing-guidance` | Concrete tool implementing the `dosing-guidance` capability | Operator implements when needed |
+| `adverse-effect-monitoring` | Concrete tool implementing the `adverse-effect-monitoring` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-pharmacist-ts/files/agent.json

@@ -0,0 +1,39 @@
+{
+  "name": "pharmacist",
+  "description": "Pharmacist reference agent bundle — drug information, interaction checks, and medication therapy management. NOT a substitute for a licensed pharmacist, physician, or other healthcare professional. Advisory only. Emits non-licensed/non-fiduciary language and includes escalation blocks. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "pharmacist",
+    "drug-reference",
+    "medication-therapy-management",
+    "advisory",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "deny"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}