principles

principles is a command for coding agents from nguyenvanduocit/research-kit. It costs 20 tokens per session (1,135 once invoked), scanned A, a copy of speckit.constitution, MIT.

A command for creating or updating a document that records the rules and principles guiding a research project, while keeping related templates aligned.

In plain words
What is it for?
Use it to define project principles from user input or existing context and apply the changes across dependent research materials.
Why use it?
It helps make research decisions explicit and prevents supporting documents from using outdated or inconsistent principles.

Command

Install

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.

agentmods
npx agentmods add commands/nguyenvanduocit/research-kit/principles
Clone the repo
git clone --depth 1 https://github.com/nguyenvanduocit/research-kit

Wrote 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.

agentmods badge for principles

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyenvanduocit/research-kit/principles.svg)](https://agentmods.dev/commands/nguyenvanduocit/research-kit/principles)
Your own site
<a href="https://agentmods.dev/commands/nguyenvanduocit/research-kit/principles"><img src="https://agentmods.dev/badge/commands/nguyenvanduocit/research-kit/principles.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,135 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.01135
Opus 5 $0.00010 $0.00567
Sonnet 5 $0.00004 $0.00227
Haiku 4.5 $0.00002 $0.00113

Measured 4d ago against content hash 128096d56139, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

principles 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 4d 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.

Origin

This is a copy

83% identical to speckit.constitution — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

templates/commands/principles.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are updating the research principles document at /principles/research-principles.md. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. [PROJECT_NAME], [PRINCIPLE_1_NAME]). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.

Follow this execution flow:

  1. Load the existing research principles template at /principles/research-principles.md.

    • Identify every placeholder token of the form [ALL_CAPS_IDENTIFIER]. IMPORTANT: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
  2. Collect/derive values for placeholders:

    • If user input (conversation) supplies a value, use it.
    • Otherwise infer from existing research context (project README, docs, prior principles versions if embedded).
    • For governance dates: RATIFICATION_DATE is the original adoption date (if unknown ask or mark TODO), LAST_AMENDED_DATE is today if changes are made, otherwise keep previous.
    • PRINCIPLES_VERSION must increment according to semantic versioning rules:
      • MAJOR: Backward incompatible changes to research methodology or ethical guidelines.
      • MINOR: New principle/section added or materially expanded guidance.
      • PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
    • If version bump type ambiguous, propose reasoning before finalizing.
  3. Draft the updated research principles content:

    • Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
    • Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
    • Ensure each Principle section covers:
      • Source Quality Standards (primary vs secondary, peer-reviewed vs non-reviewed, currency)
      • Methodology Rigor (research design, assumptions documentation, limitations acknowledgment)
      • Ethics & Bias (ethical guidelines, conflicts of interest, bias mitigation, diverse perspectives)
      • Citation Standards (proper attribution, citation format, source accessibility)
      • Analysis Quality (framework transparency, data interpretation, alternative explanations, confidence levels)
      • Report Completeness (executive summary, methodology documentation, findings support, conclusions justification)
    • Ensure Governance section lists amendment procedure, versioning policy, and quality review expectations.

Read the full file on GitHub · 86 lines

Changes

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.

  1. 4d ago First seen · 86 lines · 20 tokens per session scan A 128096d56139

Subscribe to this mod's changes

principles is a command published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 1,135 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to speckit.constitution, differing in 47 lines, and is treated as a copy.