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.
git clone --depth 1 https://github.com/harnessprotocol/harness-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/harnessprotocol/harness-kit/lineage)<a href="https://agentmods.dev/plugins/harnessprotocol/harness-kit/lineage"><img src="https://agentmods.dev/badge/plugins/harnessprotocol/harness-kit/lineage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/harnessprotocol/harness-kit/lineage"><img src="https://agentmods.dev/badge/plugins/harnessprotocol/harness-kit/lineage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lineage 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 1mo 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.
What it actually says
{
"name": "lineage",
"description": "Trace column-level data lineage through SQL, Kafka, Spark, and JDBC codebases",
"version": "0.3.0",
"category": "data-engineering",
"tags": ["sql", "data-lineage", "kafka", "spark", "jdbc", "column-level"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 94 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 8 lines scan A 15ad5beefbea
lineage is a plugin published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed today), licensed Apache-2.0. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
ecto
Compatibility namespace for the Elixir/Phoenix plugin's /ecto: commands.
llm-wiki
Build a shared Markdown knowledge base with local hybrid search and an optional evidence-linked workflow to capture task lessons, evaluate skill improvements, and apply or roll back tested changes.
database-design
Designs database schemas from requirements or reviews existing schemas for normalization, indexes, migrations, and security.
motherduck-skills
MotherDuck skills for agents and developers: use the CLI and Guides, explore schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.
motherduck-skills
MotherDuck skills for agents and developers: use the CLI and Guides, explore schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.
motherduck-skills
MotherDuck skills for Gemini CLI: use the MotherDuck CLI and Guides, explore live schemas, write DuckDB SQL, build Dives and Flights, and ship analytics apps and pipelines.