Ics Spec

C 67 completed
Library
cli / json · tiny
28
Files
10,182
LOC
0
Frameworks
5
Languages

Pipeline State

completed
Run ID
#372880
Phase
done
Progress
1%
Started
Finished
2026-04-13 01:31:02
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
60.00
Framework unique
Isolation
Last stage change
2026-05-10 03:35:34
Deduplication group #53230
Member of a group with 7 similar repo(s) — this repo is canonical view group →
Top concepts (2)
Project DescriptionData/ML
Provenance: Repobility (https://repobility.com) — every score reproducible from /scan/

AI Prompt

Create a command-line interface (CLI) tool suite based on the Instruction Contract Specification (ICS). I need three main utilities: one to validate an instruction file against the ICS rules, another to analyze an instruction file for token usage across multiple invocations, and a third for live testing against an LLM API. The project should use Python, and I need to incorporate the provided specification documents and example data structures.
python cli json llm specification validation command-line
Generated by gemma4:latest

Catalog Information

The ics-tools project provides reference tools for working with the Instruction Contract Specification (ICS).

Description

This project offers a collection of tools related to the Instruction Contract Specification (ICS), aiming to facilitate its implementation and usage. The tools are designed to support developers in understanding and utilizing ICS, making it easier to work with this specification.

الوصف

هذا المشروع يقدم مجموعة من الأدوات المتعلقة بمعيار الإجراء المكتوب (ICS)، بهدف تسهيل تنفيذه و استخدامه. تم تصميم هذه الأدوات لتعزيز فهم وتطبيق معيار ICS، مما يجعل من السهل العمل مع هذا المعيار.

Novelty

3/10

Tags

instruction-contract-specification reference-tools ics-implementation developer-support

Technologies

anthropic openai

Quality Score

C
66.9/100
Structure
67
Code Quality
58
Documentation
65
Testing
55
Practices
73
Security
100
Dependencies
60

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (33% test-to-source ratio)
  • Code linting configured (ruff (possible))
  • Consistent naming conventions (snake_case)
  • Good security practices \u2014 no major issues detected

Weaknesses

  • No LICENSE file \u2014 legal ambiguity for contributors
  • 112 duplicate lines detected \u2014 consider DRY refactoring
  • 2 'god files' with >500 LOC need decomposition

Recommendations

  • Add a test suite \u2014 start with critical path integration tests
  • Add a LICENSE file (MIT recommended for open source)

Security & Health

5.1h
Tech Debt (B)
A
OWASP (100%)
PASS
Quality Gate
A
Risk (1)
Same scanner, your repo: https://repobility.com — Repobility
MIT
License
3.5%
Duplication
Full Security Report AI Fix Prompts SARIF SBOM

Languages

json
58.8%
python
26.6%
markdown
13.8%
toml
0.4%
yaml
0.4%

Frameworks

None detected

Concepts (2)

Scored by Repobility's multi-pass pipeline · https://repobility.com
CategoryNameDescriptionConfidence
Repobility's GitHub App fixes findings like these · https://github.com/apps/repobility-bot
auto_descriptionProject DescriptionICS defines a deterministic, token-aware contract for structuring instructions provided to Large Language Models (LLMs).80%
auto_categoryData/MLdata-ml70%

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/97098.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV