cc-file-history-mod by kukaka: Claude Code mod code and design

What it does

Draws a pane, a band above the prompt, toasts
Adds /file-history
Watches Edit, Write, Bash calls and can refuse them
Hooks classic.SessionStart, session.start, ui.close
Starts processes

Good points

No network calls
Written in TypeScript
Handles errors

Code to start from

Two kinds: a starter modscode writes from the design above, and the lines of the mod's own code that draw it.

Starter (register.tsx)

import type { Register } from 'claude-code'

// Drawn like cc-file-history-mod by lixinghui (pane, band, toast), as modscode read it from the mod's code:
// https://modscode.com/gallery/kukaka-cc-file-history-mod/
// Written by modscode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
  // the pane: open it with $.ui.open({ id: 'my-pane', title: "File history" })
  on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
    const { Box, Text, Button } = $.ui.resolve(e)
    const totalFiles = '…'
    const totalEdits = '…'
    const filePath = '…'
    const length = '…'
    const filePath2 = '…'
    const filePath3 = '…'
    return (
      <Box flexDirection="column" paddingX={1} gap={1}>
        <Box flexDirection="row" gap={1}>
          <Text bold color="white">
            File history
          </Text>
          <Text color="white">
            {`${totalFiles} file, ${totalEdits} edit`}
          </Text>
          <Box flexGrow={1} />
          <Button label="Close" variant="primary" />
        </Box>
        <Box flexDirection="column" gap={1}>
          <Box flexDirection="row" gap={1}>
            <Text bold color="white">
              {filePath}
            </Text>
            <Text color="white">
              {`${length} edit`}
            </Text>
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
        </Box>
        <Box flexDirection="column" gap={1}>
          <Box flexDirection="row" gap={1}>
            <Text bold color="white">
              {filePath2}
            </Text>
            <Text color="white">
              {`${length} edit`}
            </Text>
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
        </Box>
        <Box flexDirection="column" gap={1}>
          <Box flexDirection="row" gap={1}>
            <Text bold color="white">
              {filePath3}
            </Text>
            <Text color="white">
              {`${length} edit`}
            </Text>
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
          <Box flexDirection="column" gap={1} paddingLeft={2}>
            <Box flexDirection="row" gap={1} />
          </Box>
        </Box>
      </Box>
    )
  })

  // the band above the prompt; what else goes there is drawn under it
  on('ui.render', { component: 'AbovePrompt' }, async ($, e, next) => {
    const { Box, Text, Button } = $.ui.resolve(e)
    const totalEdits = '…'
    const totalFiles = '…'
    return (
      <Box flexDirection="column">
        <Box flexDirection="row" gap={2} paddingX={1}>
          <Text color="magenta" bold>
            {`▶ File history: ${totalEdits} edit (${totalFiles} file)`}
          </Text>
          <Button label="View" hotkey="v" variant="primary" />
        </Box>
        {await next(e)}
      </Box>
    )
  })

  on('session.start', async ($, e, next) => {
    const basename = '…'
    const msg = '…'
    await $.ui.toast(`reverted ${basename}`)
    await $.ui.toast(`revert failed: ${msg}`)
    return next(e)
  })
}

The mod's own code

Shown under the mod's licence (Apache-2.0); its text is below. Keep the notice if you copy these lines.

cc-file-history-mod/hooks/register.tsx lines 940–942 · Pane

cc-file-history-mod/hooks/register.tsx:940

  on('ui.render', { component: 'Pane', requestId: PANE_ID }, ($, e) => {
    return renderPane($, e as never) as never
  })

cc-file-history-mod/hooks/register.tsx lines 550–709 · Pane

cc-file-history-mod/hooks/register.tsx:550

function renderPane($: EngineInterface, e: PaneRenderEvent) {
  type El = (props: Record<string, unknown> & { children?: unknown }) => unknown
  const { Box, Text, Button, Code } = $.ui.resolve(e as never) as {
    Box: El
    Text: El
    Button: El
    Code: El
  }

  const groups = groupByFile(edits)
  const totalFiles = groups.length
  const totalEdits = edits.length

  const closePane = async () => {
    paneOpen = false
    await $.ui.close({ id: PANE_ID })
  }

  const header = Box({
    flexDirection: 'row',
    gap: 1,
    children: [
      // The engine renders Pane chrome in a fixed dark fill in both light
      // and dark terminal modes, but the default Text colour (and the
      // Button label colour) adapts to the terminal — in a light terminal
      // it's dark, on top of the dark chrome that becomes near-invisible.
      //
      // For Text we can pin `color: 'white'` directly. For Button the
      // props don't include `color` (ButtonProps at index.d.ts:1000 only
      // exposes `dimColor`, `variant`, `plain`, `hover`), so `color:
      // 'white'` is silently dropped — that's why the buttons stay
      // invisible after a `color: 'white'` edit. The Button-level escape
      // is `variant: 'primary'`, which makes the terminal render the
      // label in the engine's accent colour (bright in both terminal
      // modes, so it always contrasts with the dark Pane chrome). We
      // mark every Button primary; Close / Show / Revert are the only
      // pressable leaves on each surface, so "the one to press" reads
      // honestly. The status-char accents (red / yellow / green) already
      // sit on the bright side of the palette and need no override.
      Text({ bold: true, color: 'white', children: 'File history' }),
      Text({
        color: 'white',
        children: `${totalFiles} file${totalFiles === 1 ? '' : 's'}, ${totalEdits} edit${totalEdits === 1 ? '' : 's'}`,
      }),
      Box({ flexGrow: 1 }),
      Button({ key: 'close', label: 'Close', variant: 'primary', onPress: closePane }),
    ],
  })

  if (totalEdits === 0) {
    return Box({
      flexDirection: 'column',
      paddingX: 1,
      gap: 1,
      children: [
        header,
        Text({ color: 'white', children: 'no edits captured yet' }),
      ],
    })
  }

  const statusChar = (rec: EditRecord): { char: string; color: string } => {
    if (rec.kind === 'delete') return { char: '×', color: 'red' }
    return rec.beforeExists
      ? { char: 'M', color: 'yellow' }
      : { char: '●', color: 'green' }
  }

const kindLabel = (rec: EditRecord): string => {
  if (rec.kind === 'edit') return 'edit'
  if (rec.kind === 'delete') return 'delete'
  return 'write'
}

  const toggleExpand = (id: number) => {
    if (expanded.has(id)) {
      expanded.delete(id)
    } else {
      expanded.add(id)
    }
    $.ui.invalidate('ui.render')
  }

  const groupBoxes = groups.map((g) => {
    const fileHeader = Box({
      flexDirection: 'row',
      gap: 1,
      children: [
        Text({ bold: true, color: 'white', children: g.filePath }),
        Text({
          color: 'white',
          children: `${g.records.length} edit${g.records.length === 1 ? '' : 's'}`,
        }),
      ],
    })

    const recordRows = g.records.map((rec) => {
      const revert = () => {
        void revertById($, rec.id)
      }
      const isOpen = expanded.has(rec.id)
      const showDiff = () => {
        toggleExpand(rec.id)
        // Kick off the diff (lazily) so the next redraw has something to
        // show. We don't await — toggleExpand's invalidate handles the
        // redraw, and the diff lands as soon as `diff -u` returns.
        if (expanded.has(rec.id)) {
          void unifiedDiff($, rec)
        }
      }
      const status = statusChar(rec)
      const rowChildren: unknown[] = []

      rowChildren.push(Text({ color: status.color, children: status.char }))
      rowChildren.push(Text({ color: 'white', children: formatTime(rec.ts) }))
      rowChildren.push(Text({ color: 'white', children: kindLabel(rec) }))

      if (rec.beforeExists && typeof rec.before === 'string') {
        const lines = rec.before.split('\n').length
        rowChildren.push(
          Text({
            color: 'white',
            children: `(${lines} line${lines === 1 ? '' : 's'} before)`,
          }),
        )
      }

      rowChildren.push(Box({ flexGrow: 1 }))

      // [Show] / [Hide] — only when we have something to diff against. Three
      // independent sources cover all rows: Edit has hunkBefore/hunkAfter
      // from the tool input; Write has before (file read) + after (input
      // content); Delete has `before` only (file content pre-deletion), and
      // `unifiedDiff` renders that as a "removed-everything" diff against
      // /dev/null.
      const hasHunk =
        typeof rec.hunkBefore === 'string' && typeof rec.hunkAfter === 'string'
      const hasFull =
        typeof rec.before === 'string' && typeof rec.after === 'string'
      const hasDelete = rec.kind === 'delete' && typeof rec.before === 'string'
      const canDiff = hasHunk || hasFull || hasDelete
      if (canDiff) {
        rowChildren.push(
          Button({
            key: `diff-${rec.id}`,
            label: isOpen ? 'Hide' : 'Show',
            variant: 'primary',
            onPress: showDiff,
          }),
        )
      } else if (rec.beforeExists && typeof rec.before === 'string') {
        // Have before but no after — the file read after `next(e)` failed.
        // Surface it explicitly so the user knows why the toggle is missing.
        rowChildren.push(Text({ color: 'white', children: '(no diff: after missing)' }))
      } else if (rec.kind === 'edit') {
        // Edit without a hunk shouldn't happen (input always carries it), but
        // be defensive — no message to avoid a misleading "missing".
        rowChildren.push(Text({ color: 'white', children: '(no diff)' }))
      }

cc-file-history-mod/hooks/register.tsx lines 961–997 · Band

cc-file-history-mod/hooks/register.tsx:961

  on(
    'ui.render',
    { component: 'AbovePrompt' },
    async ($, e, next) => {
      type BoxEl = (props: Record<string, unknown> & { children?: unknown }) => unknown
      const { Box } = $.ui.resolve(e) as { Box: BoxEl }
      const ourBand = renderBand($, e as never)
      if (ourBand === null) {
        // No band of our own — yield via next(e) so the next plugin's
        // tree (typically cc-context-mod) is preserved as-is.
        return (await next(e)) as never
      }
      // We have a band to draw. Pull next(e) to keep the other plugin's
      // tree, then compose ours below it in a column.
      //
      // `next(e)` may throw "no implementation for ui.render" if no other
      // AbovePrompt handler is registered. Catch and treat as "no others".
      let others: unknown = null
      try {
        others = await next(e)
      } catch {
        others = null
      }
      // Element-shaped = plain object with a string `type` field. Test
      // stubs sometimes return engine internals; drop those.
      const looksLikeElement =
        others !== null &&
        others !== undefined &&
        typeof others === 'object' &&
        typeof (others as { type?: unknown }).type === 'string'
      if (!looksLikeElement) return ourBand as never
      return Box({
        flexDirection: 'column',
        children: [others, ourBand],
      }) as never
    },
  )

cc-file-history-mod/hooks/register.tsx lines 797–865 · Band

cc-file-history-mod/hooks/register.tsx:797

function renderBand(
  $: EngineInterface,
  e: BandRenderEvent,
): unknown | null {
  type El = (props: Record<string, unknown> & { children?: unknown }) => unknown
  const { Box, Text, Button } = $.ui.resolve(e) as {
    Box: El
    Text: El
    Button: El
  }

  // Empty + Pane-open cases both yield — the handler `next(e)`s for us.
  if (edits.length === 0 || paneOpen) return null

  const totalFiles = groupByFile(edits).length
  const totalEdits = edits.length

  const openPane = async () => {
    try {
      const r = await $.ui.open({
        id: PANE_ID,
        title: 'File history',
        focus: true,
        closeOnEscape: true,
      })
      paneOpen = r.isPlaced === true
      if (!r.isPlaced) {
        const reason = 'reason' in r ? String(r.reason) : 'unknown'
        const hint = reason.includes('below 110 columns')
          ? ' — type /file-history once to unlock'
          : ''
        $.ui.toast(
          `file-history: pane open refused${hint}: ${reason}`,
          { timeoutMs: 6000 },
        )
      }
    } catch (err) {
      const msg = String((err as { message?: string })?.message ?? err)
      $.ui.toast(`file-history: pane open failed: ${msg}`, {
        timeoutMs: 4000,
      })
    }
    // Re-draw the band now that `paneOpen` flipped — if it didn't place,
    // the band stays visible; if it did, the band yields and the Pane
    // renders. The hotkey `v` also reaches the band, so this is the path
    // for both click and keyboard.
    $.ui.invalidate('ui.render')
  }

  return Box({
    flexDirection: 'row',
    gap: 2,
    paddingX: 1,
    children: [
      Text({
        color: 'magenta',
        bold: true,
        children: `▶ File history: ${totalEdits} edit${totalEdits === 1 ? '' : 's'} (${totalFiles} file${totalFiles === 1 ? '' : 's'})`,
      }),
      Button({
        key: 'open-pane',
        label: 'View',
        hotkey: 'v',
        variant: 'primary',
        onPress: openPane,
      }),
    ],
  })
}

Licence text (Apache-2.0)

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

What its code calls

runs programswrites filestool calls

The design, read from code

Claude — Code

reverted src/

revert failed: Edit

▶ File history: 3 edit (3 file)View v

Ask Claude…

File history

File history3 file, 3 edit

src/app.ts3 edit

Drawn from the mod's source at the commit read, not from a run: a list is drawn three times, a condition takes its first branch that draws in the desktop app, and a value only the run time knows is shown as a made-up sample (dotted underline) or left out. Colours and type are this site's.

What its code shows

Read from the source at commit 4c1679a3a4dd on 2026-10-06. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.

Decides the listing: code you can check
Entry read	Every module hooks/hooks.json names was read.cc-file-history-mod/hooks/register.tsx
Parses	Every file parses as TypeScript or JavaScript.2 files parsed
All its code is in the mod	Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod
Readable	No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs
Calls in the open	Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open
For you to weigh before installing
Where it draws	The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both
Install line	Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there
Programs on Windows	Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).cc-file-history-mod/hooks/register.tsx:458 rm (not on Windows); cc-file-history-mod/hooks/register.tsx:529 rm (not on Windows)
Network	Whether every fetch names its https host in the code.no network
Programs	Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.diff, rm
Reads and sends	Whether it both reads files or environment variables and reaches the network.reaches no network
Keys in the source	Whether the source holds what looks like an API key or a private key.no keys in the source
Licence	An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets modscode show its code; otherwise the code is linked.Apache-2.0

This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen

Install it

Check it yourself before you install it. Mods run unsandboxed, with your permissions, and modscode does not vouch for what this code does. Read the code below (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.

Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:

/plugin marketplace add kukaka/cc-mods

/plugin install cc-file-history-mod@cc-mods

This installs the marketplace's latest commit, which may not be the one read here (4c1679a3a4dd). Compare them before you install.

Ask Claude about it

With the modscode connector added, Claude can read this design, what its code reaches and its code, and build on them. Ask it like this:

Read the modscode design "kukaka-cc-file-history-mod" with its code and make me a pane like it

Search them from Claude: the MCP connector