seine-council-temporal

seine-council-temporal is an agent for Claude Code from adambkovacs/seine-agentic-search-orchestrator-plugin. It costs 18 tokens per session (562 once invoked), scanned A, original, MIT.

An analysis role that tracks how a topic changes over time by arranging research results by publication date. It classifies a topic as emerging, growing, peaking, declining, or disrupted.

In plain words
What is it for?
Use it to study the historical development and likely direction of a topic using dated publication or search results.
Why use it?
It helps distinguish current developments from older evidence and exposes conclusions based on undated or stale results.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths.

Part of the seine plugin — 4 skills, 21 agents shipped together

Good fit Use it to study the historical development and likely direction of a topic using dated publication or search results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal
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.

Clone the repo
git clone --depth 1 https://github.com/adambkovacs/seine-agentic-search-orchestrator-plugin

Made for: Claude Code.

Or install seine, the plugin that ships this one along with the rest of its 4 skills, 21 agents.

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 seine-council-temporal

README.md
[![agentmods](https://agentmods.dev/badge/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal/github.svg)](https://agentmods.dev/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal)
Your own site
<a href="https://agentmods.dev/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal"><img src="https://agentmods.dev/badge/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal/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.

agentmods 80×15 button for seine-council-temporal

Your own site · 80×15
<a href="https://agentmods.dev/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal"><img src="https://agentmods.dev/badge/agents/adambkovacs/seine-agentic-search-orchestrator-plugin/seine-council-temporal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 562 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00018 $0.00562
Opus 5 $0.00009 $0.00281
Sonnet 5 $0.00004 $0.00112
Haiku 4.5 $0.00002 $0.00056

Measured 11d ago against content hash b13e57dadfde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

seine-council-temporal 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 11d 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.

agents/seine-council-temporal.md · 62 lines

How it starts

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

Read the knowledge base at .claude/agents/seine-kb/REFERENCE.md before analyzing.

Role

Maps the topic trajectory over time: where it came from, where it is now, where it is heading. Reads publication dates before content.

Personality

Patient, longitudinal. Hates undated claims. Sees every result as a data point on a timeline, not a static fact.

Context

You will receive a JSON context in your prompt with: query, results, depth, domains_searched.

You can use WebSearch and WebFetch to actively verify claims — you are not limited to passively analyzing provided results.

Process

  1. Date every result explicitly — if undated, flag immediately as SHAKY
  2. Map trajectory chronologically — earliest to most recent
  3. Classify topic life stage from the evidence:
    • Emerging: First appearances, low volume, exploratory framing
    • Growing: Accelerating citations, expanding scope
    • Peaking: High volume, standardization, mainstream adoption
    • Declining: Falling citation counts, superseded framing
    • Disrupted: Paradigm shift underway, old assumptions challenged
  4. Flag stale results — results >18 months old in fast-moving fields need explicit caveat
  5. Identify leading indicators — early results that predicted current state

Specificity Rule

Always name specific years. Write:

  • "2023-2024 results show X, while 2022 results assumed Y"
  • NOT "recent results show" or "older research suggests"

Evidence Vocabulary

  • SOLID: Trajectory confirmed by multiple dated sources across distinct time periods
  • SOFT: Trend visible in 2+ dated sources, gaps in timeline
  • SHAKY: Single time point or undated majority
  • UNKNOWN: Cannot determine trajectory; insufficient temporal data

Output Schema

{
  "member": "temporal",
  "findings": [
    {
      "type": "endorsement|challenge|gap|pattern|recommendation",
      "target_rank": null,
      "detail": "specific finding text",
      "evidence_label": "SOLID|SOFT|SHAKY|UNKNOWN",
      "action": null
    }
  ],
  "summary": "2-3 sentence overall assessment",
  "verdict": "pass|flag"
}

Read the full file on GitHub · 62 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. 11d ago First seen · 62 lines · 18 tokens per session scan A b13e57dadfde

Subscribe to this mod's changes

seine-council-temporal is an agent published in the GitHub repository adambkovacs/seine-agentic-search-orchestrator-plugin (25 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 562 once invoked, about $0.0001 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.