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.
npx skills add honeydew-ai/honeydew-ai-coding-agents-plugins --skill relation-creationgit clone --depth 1 https://github.com/honeydew-ai/honeydew-ai-coding-agents-pluginsWrote 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/skills/honeydew-ai/honeydew-ai-coding-agents-plugins/relation-creation)<a href="https://agentmods.dev/skills/honeydew-ai/honeydew-ai-coding-agents-plugins/relation-creation"><img src="https://agentmods.dev/badge/skills/honeydew-ai/honeydew-ai-coding-agents-plugins/relation-creation/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/skills/honeydew-ai/honeydew-ai-coding-agents-plugins/relation-creation"><img src="https://agentmods.dev/badge/skills/honeydew-ai/honeydew-ai-coding-agents-plugins/relation-creation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.02553 |
| Opus 5 | $0.00023 | $0.01277 |
| Sonnet 5 | $0.00009 | $0.00511 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
relation-creation 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
Before creating relations, ensure you are on the correct workspace and branch. Use get_session_workspace_and_branch to check the current session context. For development work, create a branch with create_workspace_branch (the session switches automatically). See the workspace-branch skill for the full workspace/branch tool reference.
Overview
A Honeydew relation defines how two entities join together.
Relations are not standalone objects — they live inside the source entity's YAML as a relations: block.
Every relation connects the "many" side to the "one" side: for example, orders (many) → customers (one).
Relations enable:
- Metrics on one entity to reference attributes from another
- Cross-entity calculated attributes (Multi-Entity type)
- Filter propagation between entities in BI queries
Relations are defined on the source entity. To add a relation, use
update_objecton the entity that holds the foreign key (the "many" side).
Creation Methods
Primary: update_object on the Source Entity
There is no create_relation tool. Adding a relation means updating the source entity's YAML to include the relations: block.
Call update_object with:
yaml_text— the full updated entity YAML with therelations:blockobject_key— the entity's object key (find vialist_entitiesorget_entity)
Required permission: Editor or higher.
After Creation/Update: Display the UI Link
After a successful update_object call, the response includes a ui_url field. Always display this URL to the user so they can quickly open the object in the Honeydew application.
Remove a Relation: update_object
There is no delete_object for relations. To remove a relation, update the source entity's YAML with the relation removed from the relations: block.
- Find which entity defines the relation. The relation lives in only one entity's YAML, but it could be on either side. Use
get_entityon both entities and check which one has the relation in itsrelations:block. - Remove the target relation from that entity's
relations:list (keep all other relations intact). - Call
update_objectwith the updated YAML and the entity'sobject_key.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 196 lines · 45 tokens per session scan A 948078cad06b
relation-creation is a skill published in the GitHub repository honeydew-ai/honeydew-ai-coding-agents-plugins (39 stars, last pushed 10d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,553 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
sl
Skill "sl" from Kaelio/ktx, covering semantic layer, part 1 - schema reference, overlay sources, standalone table sources and standalone sql sources.
historic_sql_patterns
Identify recurring cross-table historic-SQL analytical intents from a bounded pattern shard and emit typed pattern evidence for deterministic wiki projection.