continue-framework

A project configuration file for an AI coding assistant. It lists enabled add-ons, where plans are stored, environment settings, status-line behavior, and actions that run around tool use.

In plain words
What is it for?
Use it to enable project add-ons, choose a plans folder, configure the status line, control tool searching, and run commands before or after agents work.
Why use it?
It keeps the assistant's project behavior in one place instead of relying on hidden or repeated settings. It also defines checks and timing actions around agent work.

Settings file for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add settings/rakovi4/continue-framework/settings
Clone the repo
git clone --depth 1 https://github.com/rakovi4/continue-framework

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin 70% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

continue-framework scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

70% identical to Ghost — 75 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/settings.json · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "enabledPlugins": {
    "frontend-design@claude-code-plugins": true,
    "jdtls-lsp@claude-plugins-official": true,
    "typescript-lsp@claude-plugins-official": true
  },
  "plansDirectory": "./ProductSpecification/plans",
  "env": {
    "ENABLE_TOOL_SEARCH": "auto:5"
  },
  "enableAllProjectMcpServers": false,
  "statusLine": {
    "type": "command",
    "command": "bash .claude/statusline.sh"
  },
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Agent",
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-timing.sh\" dispatch 2>/dev/null || true",
            "timeout": 10
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Agent",
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-timing.sh\" return 2>/dev/null || true",
            "timeout": 10
          }
        ]
      }
    ],
    "PostToolUseFailure": [
      {
        "matcher": "Agent",
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-timing.sh\" return_failure 2>/dev/null || true",
            "timeout": 10
          }
        ]
      }
    ],
    "SubagentStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-timing.sh\" subagent_start 2>/dev/null || true",
            "timeout": 10
          }
        ]
      }
    ],
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-timing-smoke.sh\" >/dev/null 2>&1 || printf '{\"systemMessage\":\"smoke checks FAILED — timing instrumentation may be broken; run: bash .claude/hooks/agent-timing-smoke.sh\"}'",
            "timeout": 30
          }
        ]
      }
    ],
 

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 88 lines scan A 3a017159d39e

Subscribe to this mod's changes

continue-framework is a settings file published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 70% identical to Ghost, differing in 75 lines, and is treated as a copy.