Skip to content
Back to search

aicode-toolkit

MarketplaceWorks with Claude CodeGitHub

Toolkit for Coding Agents to work reliably with repo of any size.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/AgiFlow/aicode-toolkit with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/AgiFlow/aicode-toolkit'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/agiflow--aicode-toolkit/badge.svg)](/listings/agiflow--aicode-toolkit)

HTML

<a href="/listings/agiflow--aicode-toolkit"><img src="/api/listings/agiflow--aicode-toolkit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requirements:

- Node.js >= 22.12 (Node 24 recommended) - an MCP-compatible agent such as Claude Code, Cursor, or Gemini CLI

1. Initialize a Workspace

# Existing project
npx @agiflowai/aicode-toolkit init

# New project
npx @agiflowai/aicode-toolkit init --name my-app --project-type monolith

This creates `templates/` and `.toolkit/settings.yaml`. Projects reference templates through `sourceTemplate` in `project.json` or `.toolkit/settings.yaml`.

2. Configure MCP

`init` can configure MCP automatically. For manual setup, add the servers you need to your agent config.

Example for Claude Code:

{
  "mcpServers": {
    "scaffold-mcp": {
      "command": "npx",
      "args": ["-y", "@agiflowai/scaffold-mcp", "mcp-serve", "--admin-enable"]
    },
    "architect-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agiflowai/architect-mcp",
        "mcp-serve",
        "--admin-enable",
        "--design-pattern-tool",
        "codex",
        "--review-tool",
        "gemini-cli"
      ]
    },
    "style-system": {
      "command": "npx",
      "args": ["-y", "@agiflowai/style-system", "mcp-serve"]
    }
  }
}

Useful flags:

- `--admin-enable`: enable admin/template-authoring tools - `--design-pattern-tool <tool>`: use an LLM to filter design patterns - `--review-tool <tool>`: use an LLM for review output

3. Verify

Ask the agent:

`What boilerplates are available?`

It should call `list-boilerplates`. If not, restart the agent.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 43 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "aicode-toolkit",
  3. "owner": {
  4. "name": "AgiFlow",
  5. "email": "vuong@agiflow.io"
  6. },
  7. "metadata": {
  8. "description": "Purpose-based AI development tools for six coding clients.",
  9. "version": "0.5.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "aicode-bootstrap",
  14. "source": "./plugins/aicode-bootstrap",
  15. "description": "Discover project boilerplates and create new applications with scaffold-mcp.",
  16. "version": "0.5.0"
  17. },
  18. {
  19. "name": "aicode-develop",
  20. "source": "./plugins/aicode-develop",
  21. "description": "Scaffold features with design-pattern guidance and post-edit review.",
  22. "version": "0.5.0"
  23. },
  24. {
  25. "name": "aicode-review",
  26. "source": "./plugins/aicode-review",
  27. "description": "Review project changes against applicable architecture and coding rules.",
  28. "version": "0.5.0"
  29. },
  30. {
  31. "name": "aicode-admin",
  32. "source": "./plugins/aicode-admin",
  33. "description": "Author templates, generators, design patterns and coding rules.",
  34. "version": "0.5.0"
  35. },
  36. {
  37. "name": "aicode-design",
  38. "source": "./plugins/aicode-design",
  39. "description": "Explore themes, supported CSS classes and UI component previews.",
  40. "version": "0.5.0"
  41. }
  42. ]
  43. }
README.md · README · 364 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # AI Code Toolkit
  2. [![npm version](https://img.shields.io/npm/v/@agiflowai/scaffold-mcp.svg?style=flat-square)](https://www.npmjs.com/package/@agiflowai/scaffold-mcp)
  3. [![License: AGPL-3.0](https://img.shields.io/badge/License-AGPL%203.0-blue.svg?style=flat-square)](https://opensource.org/licenses/AGPL-3.0)
  4. [![Discord](https://dcbadge.limes.pink/api/server/https://discord.gg/NsB6q9Vas9?style=flat-square)](https://discord.gg/NsB6q9Vas9)
  5. ![AI Code Toolkit Banner](./docs/workflow.jpg)
  6. This repo provides:
  7. - project and feature scaffolding via templates
  8. - file-level design guidance before edits
  9. - rule-based review after edits
  10. - design-system discovery for frontend work
  11. ## Why This Exists
  12. As projects scale, conventions in docs like `CLAUDE.md`, `AGENTS.md`, and style guides become hard to keep concise and consistently applied by AI agents. This toolkit moves those conventions into reusable template configs (`scaffold.yaml`, `architect.yaml`, `RULES.yaml`) so agents can discover only the relevant guidance when needed.
  13. ## Purpose-based plugins
  14. For toolkit users who prefer an agent plugin, install only the workflows you need: `aicode-bootstrap` (project creation), `aicode-develop` (features and patterns), `aicode-review` (rules-based review), `aicode-admin` (authoring reusable configuration), or `aicode-design` (frontend discovery). Self-contained plugin roots are under [`plugins/`](plugins/) and work with the Claude Code/Cowork marketplace, Codex marketplace, and local Gemini extension installation; Cursor/Grok and Cowork's local stdio runtime still need client acceptance tests. Read the [installation and compatibility guide](docs/plugins/README.md) before use. These bundles group workflows rather than restrict tool access.
  15. Initialize the **consumer project before starting** a scaffold-backed plugin with interactive `npx -y @agiflowai/aicode-toolkit@2.0.0 init --skip-mcp`; plugin installation does not supply templates. Keep MCP server cwd in the consumer workspace. Published style-system `0.2.0` currently ignores some discovery filters until the dispatch fix is released. See [compatibility](docs/plugins/compatibility.md).
  16. ## Quick Start
  17. Requirements:
  18. - Node.js >= 22.12 (Node 24 recommended)
  19. - an MCP-compatible agent such as Claude Code, Cursor, or Gemini CLI
  20. ### 1. Initialize a Workspace
  21. ```bash
  22. # Existing project
  23. npx @agiflowai/aicode-toolkit init
  24. # New project
  25. npx @agiflowai/aicode-toolkit init --name my-app --project-type monolith
  26. ```
  27. This creates `templates/` and `.toolkit/settings.yaml`. Projects reference templates through `sourceTemplate` in `project.json` or `.toolkit/settings.yaml`.
  28. ### 2. Configure MCP
  29. `init` can configure MCP automatically. For manual setup, add the servers you need to your agent config.
  30. Example for Claude Code:
  31. ```json
  32. {
  33. "mcpServers": {
  34. "scaffold-mcp": {
  35. "command": "npx",
  36. "args": ["-y", "@agiflowai/scaffold-mcp", "mcp-serve", "--admin-enable"]
  37. },
  38. "architect-mcp": {
  39. "command": "npx",
  40. "args": [
  41. "-y",
  42. "@agiflowai/architect-mcp",
  43. "mcp-serve",
  44. "--admin-enable",
  45. "--design-pattern-tool",
  46. "codex",
  47. "--review-tool",
  48. "gemini-cli"
  49. ]
  50. },
  51. "style-system": {
  52. "command": "npx",
  53. "args": ["-y", "@agiflowai/style-system", "mcp-serve"]
  54. }
  55. }
  56. }
  57. ```
  58. Useful flags:
  59. - `--admin-enable`: enable admin/template-authoring tools
  60. - `--design-pattern-tool <tool>`: use an LLM to filter design patterns
  61. - `--review-tool <tool>`: use an LLM for review output
  62. ### 3. Verify
  63. Ask the agent:
  64. `What boilerplates are available?`
  65. It should call `list-boilerplates`. If not, restart the agent.
  66. ## Repo Layout
  67. ```text
  68. AI agent
  69. ├─ scaffold-mcp
  70. ├─ architect-mcp
  71. ├─ style-system
  72. └─ one-mcp
  73. ↓
  74. templates/
  75. ├─ scaffold.yaml
  76. ├─ architect.yaml
  77. └─ RULES.yaml
  78. ```
  79. ### scaffold-mcp
  80. Generates projects and feature boilerplate from templates.
  81. Core tools:
  82. - `list-boilerplates`
  83. - `use-boilerplate`
  84. - `list-scaffolding-methods`
  85. - `use-scaffold-method`
  86. Admin tools:
  87. - `generate-boilerplate`
  88. - `generate-feature-scaffold`
  89. - `generate-boilerplate-file`
  90. ### architect-mcp
  91. Provides file-specific patterns before edits and reviews changes against `RULES.yaml`.
  92. Core tools:
  93. - `get-file-design-pattern`
  94. - `review-code-change`
  95. Admin tools:
  96. - `add-design-pattern`
  97. - `add-rule`
  98. ### style-system
  99. Provides theme, CSS class, and component discovery tools.
  100. Core tools:
  101. - `list_themes`
  102. - `get_css_classes`
  103. - `get_component_visual`
  104. - `list_shared_components`
  105. - `list_app_components`
  106. ### one-mcp
  107. Provides progressive tool discovery to reduce MCP prompt overhead.
  108. ## Typical Workflow
  109. ### Create a Project
  110. ```text
  111. User: "Create a Next.js app called dashboard"
  112. Agent:
  113. 1. list-boilerplates
  114. 2. use-boilerplate
  115. 3. Project is generated
  116. ```
  117. ### Add a Feature
  118. ```text
  119. User: "Add a products API route"
  120. Agent:
  121. 1. list-scaffolding-methods
  122. 2. use-scaffold-method
  123. 3. Feature files are generated
  124. ```
  125. ### Edit a File Safely
  126. ```text
  127. User: "Add a products page"
  128. Agent:
  129. 1. get-file-design-pattern
  130. 2. edit the file using the returned patterns and rules
  131. 3. review-code-change
  132. 4. fix any violations
  133. ```
  134. ### Style a Component
  135. ```text
  136. User: "Style the button with our theme colors"
  137. Agent:
  138. 1. get_css_classes
  139. 2. list_shared_components
  140. 3. update the component
  141. 4. get_component_visual
  142. ```
  143. ## Template Structure
  144. ```text
  145. templates/
  146. └── nextjs-15/
  147. ├── scaffold.yaml
  148. ├── architect.yaml
  149. ├── RULES.yaml
  150. └── boilerplate/
  151. ```
  152. ### `scaffold.yaml`
  153. Defines boilerplates and feature scaffolds.
  154. ```yaml
  155. boilerplates:
  156. - name: nextjs-15-app
  157. description: 'Next.js 15 with App Router'
  158. targetFolder: apps
  159. includes:
  160. - boilerplate/**/*
  161. features:
  162. - name: add-route
  163. description: 'Add route with page and layout'
  164. variables_schema:
  165. name: { type: string, required: true }
  166. includes:
  167. - features/route/**/*
  168. ```
  169. ### `architect.yaml`
  170. Defines file-level patterns that should be shown before edits.
  171. ```yaml
  172. patterns:
  173. - name: server-component
  174. description: 'Default for page components'
  175. file_patterns:
  176. - '**/app/**/page.tsx'
  177. description: |
  178. - Use async/await for data fetching
  179. - Keep components focused on rendering
  180. - Move business logic to server actions
  181. ```
  182. ### `RULES.yaml`
  183. Defines review rules. Rules can be inherited from a global `templates/RULES.yaml`.
  184. ```yaml
  185. version: '1.0'
  186. template: typescript-lib
  187. rules:
  188. - pattern: src/services/**/*.ts
  189. description: Service Layer Implementation Standards
  190. must_do:
  191. - rule: Create class-based services with single responsibility
  192. codeExample: |-
  193. export class DataProcessorService {
  194. async processData(input: string): Promise<ProcessedData> {
  195. // Implementation
  196. }
  197. }
  198. - rule: Use dependency injection for composability
  199. must_not_do:
  200. - rule: Create static-only utility classes - use functions
  201. codeExample: |-
  202. // ❌ BAD
  203. export class Utils {
  204. static format(s: string) {}
  205. }
  206. // ✅ GOOD
  207. export function format(s: string): string {}
  208. ```
  209. ## Project Types
  210. ### Monorepo
  211. Each project references its template in `project.json`.
  212. ```text
  213. my-workspace/
  214. ├── apps/
  215. │ └── web-app/
  216. │ └── project.json
  217. ├── packages/
  218. │ └── shared-lib/
  219. │ └── project.json
  220. └── templates/
  221. ```
  222. ### Monolith
  223. Monoliths use `.toolkit/settings.yaml`.
  224. ```yaml
  225. version: '1.0'
  226. projectType: monolith
  227. sourceTemplate: nextjs-15
  228. ```
  229. ## Built-in Templates
  230. Included templates:
  231. | Template | Stack | Includes |
  232. | ------------------------ | ---------------------- | ------------------------------------------ |
  233. | `nextjs-drizzle` | Next.js 15, App Router | TypeScript, Tailwind 4, Drizzle, Storybook |
  234. | `typescript-lib` | TypeScript Library | ESM/CJS, Vitest, TSDoc |
  235. | `typescript-mcp-package` | MCP Server | Commander, MCP SDK |
  236. ## Custom Templates
  237. For template authoring, start from an existing repo or template and use the admin prompts:
  238. ```text
  239. /generate-boilerplate
  240. /generate-feature-scaffold
  241. ```
  242. For design/rule authoring, use:
  243. - `add-design-pattern`
  244. - `add-rule`
  245. ## Supported Agents
  246. | Agent | Config Location | Status |
  247. | -------------- | ----------------------- | --------- |
  248. | Claude Code | `.mcp.json` | Supported |
  249. | Cursor | `.cursor/mcp.json` | Supported |
  250. | Gemini CLI | `.gemini/settings.json` | Supported |
  251. | Codex CLI | `.codex/config.json` | Supported |
  252. | GitHub Copilot | VS Code settings | Supported |
  253. | Windsurf | - | Planned |
  254. ## Packages
  255. | Package | Description |
  256. | ---------------------------------------------------- | ----------------------------------- |
  257. | [@agiflowai/aicode-toolkit](./apps/aicode-toolkit) | CLI for init and config sync |
  258. | [@agiflowai/scaffold-mcp](./packages/scaffold-mcp) | Scaffolding server |
  259. | [@agiflowai/architect-mcp](./packages/architect-mcp) | Pattern and review server |
  260. | [@agiflowai/style-system](./packages/style-system) | Design-system server |
  261. | [@agiflowai/one-mcp](./packages/one-mcp) | MCP proxy for progressive discovery |
  262. ## Contributing
  263. See [CONTRIBUTING.md](./docs/CONTRIBUTING.md).
  264. ## License
  265. [AGPL-3.0](./LICENSE)
  266. ---
  267. [Issues](https://github.com/AgiFlow/aicode-toolkit/issues) · [Discord](https://discord.gg/NsB6q9Vas9) · [Website](https://agiflow.io)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.